Performance problems in CMake support
aleixpol at gmail.com
Mon Mar 31 22:39:42 UTC 2008
Yes, I've ran callgrind too and it seems that this qregexp is spent by
the finders so there is no much to do on the code.
My plan is to bring cache support which I think will bring the needed speed.
On 3/31/08, Andreas Pakulat <apaku at gmx.de> wrote:
> just wondering wether there are any plans to improve the cmake parser's
> performance? I've just noticed that it takes about 15-20 seconds to
> parse KDevelop4 when starting KDevelop and a quick (not finished)
> callgrind profile shows that a lot of time is spent in QRegExp and Co.
> You will give someone a piece of your mind, which you can ill afford.
> KDevelop-devel mailing list
> KDevelop-devel at kdevelop.org
More information about the KDevelop-devel