On Sat, 2008-12-27 at 15:12 +0100, Michał Sawicz wrote: > Dnia 2008-12-26, pią o godzinie 16:05 -0500, Aaron Bockover pisze: > > Honestly, those symptoms don't sound related to sqlite/your library. > > If all you are doing is clicking "next", nothing much happens DB > > wise... > > I once did look into some of banshee's queries. The biggest overhead I > noticed were: > > a) shuffling - Banshee calculates RAND() for every record every time > there's a song switch while selecting COUNT(*) and then selecting a > record "... LIMIT RAND() * $count, 1" would be much faster. Another > approach would be to cache a randomized playlist (and even possibly > display it randomized). Unless that has changed since last time I > checked that, that's something that could definitely see some > improvement. > > b) smart playlists - again - on every song change, the smart playlists > are recalculated just to display their count when we don't want anything > else from them. Amr's log (available here : http://bugzilla.gnome.org/show_bug.cgi?id=565730 ) seems to tell the same story : 1113ms to refresh the "Unheard" smart playlist, about 500ms to select the next random track. > amrhassan - try disabling the smart playlist extension (and restart > banshee afterwards, it doesn't seem to stop calculating smart playlists > without that). There's no smart playlist extension. You'd have to delete all smart playlists. -- Bertrand Lorentz <bertrand lorentz gmail com> > http://flickr.com/photos/bl8/ <
Attachment:
signature.asc
Description: This is a digitally signed message part