W. Martin Borgert wrote:
> On 2009-05-26 08:39, Frank Mehnert wrote:
>   
>> On Monday 25 May 2009, Noah Kantrowitz wrote:
>>     
>>> The sort version is yes, Genshi is slower in pretty much every case
>>> than clearsilver. What kind of slowdown are you talking about? Seeing
>>> 50ms longer to render a page seems plausible, but not 5000ms.
>>>       
>> Right, 50ms longer would be ok. Unfortunately last time I didn't do
>> any measurements but during the last experiment it took several
>> seconds to render the timeline (10 days back) in the browser. After
>> switching back to trac 0.10 this time was reduced to below 0.5 seconds.
>>     
>
> Just out of curiosity: Why has genshi been selected for trac and
> not e.g. cheetah, which seems to be much faster?

See http://trac.edgewall.org/wiki/TracDev/ApiChanges/0.11#Genshi for 
some background.

>  Are there any
> ideas/plans to improve genshi performance?
>   

The recent Genshi trunk (0.6dev) had seen a few performance 
optimization, so you may want to try it out:
http://genshi.edgewall.org/wiki/Download#LatestDevelopmentSourceCode

The problem of Genshi performance is a real one for any potentially big 
pages like the timeline, long source files, big changesets ... And yes, 
in those cases the speed penalty is rather in seconds, not in ms. It 
might be a worthy long term project for someone wanting to contribute to 
Trac, to either improve drastically the Genshi performance or to allow 
the use of alternative template engines in Trac (at the cost of breaking 
some advanced uses of Genshi, like the themes stuff).
An intermediate, shorter term approach, could be to pass more data as 
"opaque" to Genshi (in particular in the source browser and the 
changeset view).

But Genshi is not the only thing to blame in performance degradations 
for Trac 0.11. In particular, there are a few tickets 
(http://trac.edgewall.org/ticket/7490, 
http://trac.edgewall.org/ticket/7785) that indicate there's something 
going really wrong in some setups, and understanding and fixing these 
problems is high priority for the next maintenance release (0.11.5).
We also think about doing some profiling, at last, and that could reveal 
other bottlenecks ;-)

-- Christian

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups "Trac 
Users" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/trac-users?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to