[PATCH] Speeding up kdebug

Nicolas Goutte nicolasg at snafu.de
Tue Oct 14 22:07:21 BST 2003


No, it is not one-time only or we would have not had this big kdebug 
discussion for just one entry in kdebug.areas. (I have counted 60 calls in my 
.X.err for one hour of up-time. I do not know if it is typical or not.)

Probably something like your patch is the best solution until KDE 4, as 
otherwise we need to find a solution for kdebugdialog (which is not as easy 
as I first thought.)

As for using kde-optimize, well, sorry, I had not thought about it. And also 
as it was a big design change (no kdebug.areas anymore), I would probably not 
used it either.

Have a nice day!

--- Original Message ---
Subject:  Re: [PATCH] Speeding up kdebug
From:     Dirk Mueller <mueller () kde ! org>
Date:     2003-10-14 19:38:05


On Tuesday 14 October 2003 20:48, Nicolas Goutte wrote:

> The idea is to speed up kdebug by parsing not at runtime but at compile
> time. (On my computer, getDescrFromNum needs 1 or 2 ms instead of 19 or 20
> ms. It can change depending system and compiler optimization or because of
> slow or busy disks.)

Note this is a one-time cost only, that means not at each invokation, only 
during the first. 

Assuming that there was some good reason for making it runtime configurable at 
all (I don't know kdebug), attached a patch that reduces the runtime of the 
above mentioned function from 14ms down to 3ms. 

BTW, kde-optimize would have been the correct place..
(...)




More information about the kde-core-devel mailing list