kdevelop starting/closing performance issues

[Matt Rogers]

On Tuesday 26 April 2005 02:23 pm, Alexander Neundorf wrote:
> Hi,
>
> I'm using kdevelop from kde 3.4 among others on a PIII/450 256 MB.
> Two things are slow:
> 1) starting kdevelop
>
> It seems most of the time is spent loading the files. AFAIK for every file
> a kate/kwrite part is created and loaded. Is actually also the plugin
> dlopen()ed for each file again ? I guess also each of the source files is
> parsed, for highlighting, the class tree etc.
> It could be much faster if the files were loaded on demand at the moment
> when the file becomes the first time the active document. But this seems to
> be problematic with kate/kwrite part design.
>
> 2) closing kdevelop
>
> This can take almost as long as opening all the files. It seems that for
> every file which is closed a lot of stuff is going on. Can there something
> be done about this ?
> With maybe 50 open files this can take up to maybe 20 seconds ( I didn't
> measure, but it's more than 10 seconds).
>
> Bye
> Alex

I also took out some qApp->processEvents() hacks from kmdi, and noticed a bit 
of non-responsiveness here, but I don't think it's the cause for the greater 
slowdown.

Matt
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20050426/7b6692bd/attachment.sig>