KConfig sync speedup patch rev 1

[Benjamin Meyer]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Wednesday 10 September 2003 11:16 am, Josef Weidendorfer wrote:
> On Wednesday 10 September 2003 14:23, Ian Reinhart Geiser wrote:
> > On Wednesday 10 September 2003 08:08 am, Waldo Bastian wrote:
> > > > Now we have this blindingly
> > > > slow datastructure and archatecture that seems to be all of our speed
> > > > issues.
> > >
> > > Do you have any data on this?
> >
> > Well every test I have done shows the greatest time in all operations is
> > in KConfig::putData(..).  The real painful operation is QMap::operator[]
> > which is noted in the docs as a slow operation.  The end goal of my
> > refactoring
>
> I can't find that note.
> QMap's insert/remove/search complexity is logarithmic to the number of
> entries in the map, as it uses a tree structure, so it can't be that slow.
> Though, I noted myself that there are a lot of Unicode string comparations
> when using QMaps (I'm using QMap myself in KCachegrind).
> Perhaps you get it faster by using hash tables, but you always should try
> to meassure real times here to check the improvement.
>
> Josef

When removing unessary keys (like kautoconfig does) does this reduce the
number of actualy entries in the map (thus incresing speed) or are the keys
simply marked to not be written, but still parsed?

- -Benjamin Meyer

- --
Public Key: http://www.csh.rit.edu/~benjamin/public_key.asc
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE/X08c1rZ3LTw38vIRAia3AKCY/XOzr8c2GMpPw0/PuTxTlS0spACgs/Ra
nP99+TAJNlaXqEdELSIvpRU=
=c42t
-----END PGP SIGNATURE-----