DEC
6
2005

Stupid me

If we now spend 1/3 of time in the dynamic linker, of course it helps not forgetting to run prelink. Here's the second bootchart for KDE again (and the Xfce one for comparison, although that one doesn't really change).


I wonder if we can call it a draw for now :).

DEC
6
2005

And the fastest starting desktop environment is ...

No, not really. But it's quite close (and it actually also depends on how you twist the benchmark ;) ). When my desktop machine could start KDE in less than 4 seconds I was curious what would the situation be with this slow laptop, the one which started KDE in 5-6 seconds at aKademy. But that was with almost no fonts installed, no XIM, no wallpaper, the simplest splash and other tricks from the KDE performance tips page.

DEC
2
2005

4 seconds

[13:17:58] <Seli> boy, this machine sucks ... how am I supposed to benchmark anything if it fires up KDE in 3.7 seconds?

NOV
28
2005

Reply to mailing list

Strange that there are still many people who care if a mailing list changes Reply-To header to point to the mailing list (usually called Reply-To munging) or not. Like if that matters ... I'm not even sure which mailing lists I'm subscribed to do or don't do that.

NOV
22
2005

NULL

From the KOrganizer coding style guidelines: "A null pointer is 0, not 0l, 0L or NULL. Once again, this is C++, not C." Hmmm. If you get bored sometimes, try to compile with gcc something like "void foo( int ); ... foo( NULL );" and see what happens. And then what happens with "foo( 0 );" (and yes, I remember fixing a bug in KDE caused by this). Ok, NULL is not what it really should be, but C/C++ have many small weird things (ever wondered why binary operators | and & have so stupid priority? It's called backwards compatibility lasting for more than 30 years). Moreover, I wonder, why are symbolic constants C but not C++?

NOV
18
2005

Speaking of fontconfig bugs ... and using unstable versions

In case you have upgraded your fontconfig packages to those I provided in my blog entry about new fontconfig version, you may have run into KDE bug #116176 with the KDE3.5rc1 packages. Well, I warned you. That sometimes happens with unstable versions. I suggest you downgrade again or do your own build of newer fontconfig version or do whatever you want to do, but I'm not going to provide newer packages. It's still an unstable version after all.

NOV
7
2005

Yet another fonts performance tip

Is it just me or do the blog categories on kdedevelopers.org never match what I want to say? Well, nevermind. The latest performance tip brought to you by SUSE KDE developers (don't ask, I very likely don't know anyway) is here:

OCT
26
2005

On measuring memory usage #2

Hmm ... I should wish things more often. I complained about the lack of any usable memory reporting tool on Linux, and only a couple of days later I discovered exmap. Unlike e.g. top with its number of useless memory usage values, exmap has only three of them.

SEP
27
2005

Fontconfig's biggest bug

Update: The fontconfig packages linked from this post seem to cause KDE bug #116176 with KDE3.5 packages. Well, I warned you.

SEP
15
2005

On measuring memory usage

Oh boy. Gwenview uses 83% more memory than Kuickshow (http://kde-apps.org/content/show.php?content=9847 - the last comment as of now). BTW I especially like the "83%" part - it's just one case and the measurement is imprecise, but it can't be "about 80%" or "almost double". Reminds me of all those "hair 74% stronger" ads. Anyway.

Pages