On Thu, Dec 03, 2009 at 10:01:14AM -0800, Gabriel Burt wrote: > That might prevent your thread from getting blocked, but it shouldn't > speed up the actual Next() call. The long Next () call has been > discussed (and likely solved) recently on bugzilla. See: > > https://bugzilla.gnome.org/show_bug.cgi?id=581103 How large of a library would you expect to display a Next delay? I recently converted to Banshee and have noticed major delays in Next. My library is quite a bit larger than the one in the bugzilla above: ~58K songs. They query in the bug report [1] runs very quickly on my library: ross turalyon:~/.config/banshee-1$ time sqlite3 ./banshee.db "SELECT COUNT(*), > SUM(CoreTracks.FileSize) FROM CoreTracks,CoreAlbums,CoreArtists, > CoreSmartPlaylistEntries WHERE CoreArtists.ArtistID = > CoreTracks.ArtistID AND > CoreAlbums.AlbumID = CoreTracks.AlbumID AND > CoreSmartPlaylistEntries.TrackID > = CoreTracks.TrackID AND CoreSmartPlaylistEntries.SmartPlaylistID = > 3;" 52533|263138304276 real 0m0.519s user 0m0.460s sys 0m0.060s I really like banshee because it's stable with my library, but it feels very sluggish. The above makes me think that the delay is something else. Ross [1] https://bugzilla.gnome.org/show_bug.cgi?id=581103#c11 -- Ross Vandegrift ross kallisti us "If the fight gets hot, the songs get hotter. If the going gets tough, the songs get tougher." --Woody Guthrie
Attachment:
signature.asc
Description: Digital signature