[KimDaBa] Profiling Kimdaba startup
Robert L Krawitz
rlk at alum.mit.edu
Tue Jan 4 07:40:14 CET 2005
From: "Jesper K. Pedersen" <blackie at blackie.dk>
Date: Tue, 4 Jan 2005 07:46:37 +0100
Robert, thx for your profiling.
As it looks now, I can't see that there are any thing else I can do
to speed up things, except rewritting to a real database. Well I
could delay loading the plugins, but it is a constant of 500msec in
your profiling, so I don't see much gained there either.
Rewritting to a real db would be a huge job, and currently I dont
see it worth it to save at most 2.5+1=3.5 secs. People with 50.000
images might disagree, but we aren't really there yet (at least
that is not what I hear from most kimdaba users), and once we are
there, computers are likely so much faster that the 25 secs has
The other possibility would be a faster XML parser, or getting
Trolltech to improve their XML parser.
I don't think this is critical. The machine I ran this on is quite
slow by today's standards (1 GHz). By my calculation, on a 3 GHz
machine (midrange by today's standards), startup for 50K messages
would take about 10 seconds. I suspect that getting a database (even
a light weight database) to start up in much less than that amount of
time wouldn't be that easy, either.
The only fly in the ointment is if processors gain more parallelism
rather than single-threaded performance. Even if single threaded
performance simply stays at current levels, though, this doesn't look
to be a major problem.
Robert Krawitz <rlk at alum.mit.edu>
Tall Clubs International -- http://www.tall.org/ or 1-888-IM-TALL-2
Member of the League for Programming Freedom -- mail lpf at uunet.uu.net
Project lead for Gimp Print -- http://gimp-print.sourceforge.net
"Linux doesn't dictate how I work, I dictate how Linux works."
More information about the KimDaBa