increase performance of background parser
david.narvaez at computer.org
Tue Nov 1 21:17:57 UTC 2011
On Tue, Nov 1, 2011 at 4:08 PM, Andreas Pakulat <apaku at gmx.de> wrote:
> As Sven already said increasing the number of threads won't help, it may
> even hurt due to lock-contention (i.e. some of the threads need to wait
> more/longer before they can continue).
> The only things that can help speeding up kdevelop's parsing performance
> significantly at the moment are: SSD to remove all IO-bottlenecks and
> having a CPU thats running with >3GHz so the code can be executed
> That being said, if you want to help find possible new bottlenecks in
> the codebase (there are some known ones which are unfortunately hard to
> fix) then run kdevelop in valgrinds callgrind and/or helgrind and upload
> the resulting data somewhere for the devs to look at. Make sure to build
> kdevelop in RelWithDebInfo mode so optimizations are applied but
> debug-info is somewhat retained.
I can confirm there's something weird going on with background
parsers. I actually have to cancel it ASAP before getting to work, and
I haven't had a chance to check exactly what happens there, but it
tends to lock my computer up.
David E. Narvaez
More information about the KDevelop-devel