Andreas Pflug <[email protected]> wrote: > Using the outline skin on Debian 5.0, I see mixxx consuming 13 % CPU, > and xorg 32% even when there's no visual change. > > Digging a little on the performance issues mentioned in the wiki, I > found that preventing ControlObject from changing unchanged values does > the trick, see attached trivial patch against trunk. It reduces xorg > CPU usage to a minimum when there's no display update.
Blimey. Sometimes the simplest optimisations are staring you in the face. Nice one Andreas. Can I request that this is put into 1.7.0, I know it's late in the day but it looks totally safe to me and definitely worth doing. > As soon as I play, the cpu usage rises again (mostly in xorg, caused by > wVuMeter updates), which I reduced drastically by using repaint() > instead of update() in WWidget::setValue(). I'm not familiar with the difference between repaint() and update(), might there be any side-effects here other than the speed gain? Eg LEDs? Ben ------------------------------------------------------------------------------ Crystal Reports - New Free Runtime and 30 Day Trial Check out the new simplified licensign option that enables unlimited royalty-free distribution of the report engine for externally facing server and web deployment. http://p.sf.net/sfu/businessobjects _______________________________________________ Mixxx-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mixxx-devel
