I've upgraded our main server tonight [from trunk], and the rendering
for the Timeline view has suddenly become hardly usable.
From about 2-3 seconds with the previous version [4710], the rendering
now takes over 10 seconds [4757]. The server is running Apache
2.0.58/Python 2.4/mod_python, with a LDAP authentication backend and
SQLite for the DB backend.
I run a couple of test on my laptop and tracd a couple of minutes ago
with wget: w/ the very same Timeline events, it takes ~ 1.5 seconds to
retrieve the timeline with [4682], ~ 2.0 seconds with [4878]
I've run all the tests over 10 times for each configuration, and no
change has been made in the wiki or in the repository - so resync
should not be a source of slowness.
Is this a known issue?
Cheers,
Manu
I should have mentionned that while the web client is waiting for the
server response, 'top' command shows that a single Apache process eats
up 99% of the CPU time [Pentium-III 1GHz] for 10 seconds.
Cheers,
Manu
Ok, I've been able to identify the culprit... It's because r4737 and
4743 changed the way to produce the ticket summaries, by requiring the
ticket context's full-blown resource instead of the (already available)
ticket summary.
I expected some performance impact, but not that much, so I'll find a
way to fix that. Sorry for the inconvenience!
-- Christian
Not a big deal: I just wanted to red-flag this issue before 0.11 release ;-)
Cheers,
Manu
Ok, this should be fixed with r4768, please try out.
I also tried to cache the resources, but the speed improvements were not
that great and I'm not sure of all the implications of such a cache, so
I finally didn't commit it.
If you have lots of attachments, #4312 will hurt the performance as well ...
-- Christian
> Ok, this should be fixed with r4768, please try out.
Timeline rendering has decreased from 26.5 seconds down to 9.5
seconds, so this is a major improvement.
It still a bit slow, but it's much closer to the user experience we
were used to get before the regression. We probably need a faster
server though ;-)
Thanks a lot,
Manu
> I also tried to cache the resources, but the speed improvements were not
> that great and I'm not sure of all the implications of such a cache, so
> I finally didn't commit it.
>
> If you have lots of attachments, #4312 will hurt the performance as well ...
>
> -- Christian
>
> >
>
--
Manu