Re: [Banshee-List] Performance for Banshee 2.0



I'm also having some performance issues. I'm on the daily from ubuntu ppa, but I also experienced this slowness on 1.80.

When I skip tracks, the next track starts playing instantly, but it takes at least 3-4 seconds to highlight (turn text to bold, and add play icon to) the next track. Furthermore, it takes another 3-4 seconds before the Progress-bar, the track info on the status-bar, and the cover art are updated. When the progress bar updates, its usually already on 0:07, or 0:08.

Is this normal? 

The library is about 40,000. The box is reasonably fast, an AMD 64 X2, 4200+, plenty of RAM, fast disk, no compiz, no other performance problems. Its Ubuntu 10.04 so i'm on sqlite 3.6.22-1.

Neil.

On 11 December 2010 11:15, osfight.de <linux osfight de> wrote:
I did not understood what you meant but reading this entry on omgubuntu.com clarifies things. I guess we can discuss any major performance issues once I have ruled out all known and solved bugs related to SQL.

On 12/06/2010 03:40 AM, gnomeuser gmail com wrote:


2010/12/5 osfight.de <linux osfight de>
Any chance that the general performance for the final Banshee release
2.0 experiences a significant improvement? I know it came up here
several times that for larger libraries (10000+) the responsiveness is
rather a slow motion show than a smooth experience.

Even simplest tasks such as scrolling trough a larger playlist and
clicking on single songs seems to be unnecessarily slowed down.
Especially for Meego devices, I feel this is a major issue that needs to
be addressed and would have a high impact on user experience.

The best way you can help out is:

a) ensuring that you are on a non-broken SQLite (on the 3.7.x series this would mean 3.7.3)
b) running the daily ppa and helping identify specific slow scenerios we can fix. e.g.:

Examples of such bugs:

I've added a few little basic hints for performance problems to my pet project the Common Banshee Questions page.


Finally I have a little patch to Hyena that will fire a log message every time you hit an SQL query longer than a given number of milliseconds which I personally find informative as to when we are doing a lot of work. You could apply that.

_______________________________________________ banshee-list mailing list banshee-list gnome org http://mail.gnome.org/mailman/listinfo/banshee-list (unsubscribe here)


_______________________________________________
banshee-list mailing list
banshee-list gnome org
http://mail.gnome.org/mailman/listinfo/banshee-list  (unsubscribe here)



[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]