background parser

[Milian Wolff]

On Tuesday 06 December 2011 11:25:36 Mahmood Naderan wrote:
> >- What's your KDevelop version?
> 
> 4.2.3

try master, it could be faster already due to some optimizations I added 
there.

> >- How many projects does your session have?
> 
> 1
> 
> >- Do you remember if your session has crashed before?
> 
> yes, but after normal close and open the background parser works from 10
> minutes At first time after crash, I thought it si normal.

yes that it is.

> crashed->open kdevelop->background parser (10 min)->normal close->open
> kdevelop->background parser (10min)

ok good.

> >- If you start KDevelop from the console, you'll see a lot of output
> >while the background parser works. Do you see several lines saying
> >ALREADY UP TO DATE?
> 
> yes a lot.
> 
> kdevelop(1604)/kdevelop (cpp support) CPPInternalParseJob::run: ===--
> ALREADY UP TO DATE --===>

<snip>

ok, so the cache *does* work, I wonder what else keeps you waiting for so 
long.

> >However it still needs to check each file to see wether it needs to be
> >reparsed or not, depending on the amount of files and access speed to
> >them this can take more or less time
> >But generally this is not a huge problem, since you can already work
> >with KDevelop while this is running in the background
> 
> I agree with that because the src/ contains 2047 files. but isn't
> there any way to reduce parser cpu usage?

this is *not* much at all, kdevplatform alone has 7.7k files and opens in a few 
seconds for me.

which brings me back to the beginning: please try current master. if it is 
still slow, please profile kdevelop with your project, and tell us the results. 
Alternatively: is your project open source, can we/I get our hands on it to 
test it?

bye
-- 
Milian Wolff
mail at milianw.de
http://milianw.de