Hi ANdreaT On Jul 10, 2:17 am, Andrea Tomasini <[email protected]> wrote: > On 10 Jul, 2009, at 8:56 , openwfefan wrote: > > > Hi ANdreaT > > Hi There :-) > > > > > v) Our S/W guru, looked at the performance traces and said the work > > around is as follows: > > > In our httpd.conf, he did the following changes > > > Alias /trac/chrome/common/ "/usr/lib/python2.5/site-packages/trac/ > > htdocs/" > > Alias /trac/chrome/site/ "/var/tracdb/tracenv/htdocs/" > > > <Location "/trac/chrome/common"> > > SetHandler None > > </Location> > > <Location "/trac/chrome/site"> > > SetHandler None > > </Location> > > > With the above changes, the static content did not go through > > mod_python and hence the speed was vastly improved especially for the > > agilo trac instance. Speed improvement was also seen for the non-agilo > > enabled trac instance. > > Thanks for sharing this, it is a good best practice to let apache > serve static content. It is the way we do it in our hosted service :-) > > > To make a long story, short, to improve agilo performance make sure > > that the static content is server by apache and is not served by the > > trac server > > > On _why_ exactly enabling agilo would slow down the serving of static > > content, is left as an exercise to the reader :-) > > Well the reason is that trac doesn't have that many images, CSS and > Javascript files, Agilo does. In some cases we experienced also that > the sidebar, which get's loaded with JQuery partial load is a reason > for slowdowns.
That is not true in the case we tried. I disabled the Advanced GUI, so the images were the same, there was no agilo sidebar. The only addition was agilo.css > > I was expecting something specific to Agilo, apparently the reason for > the slowdown are related to "Static" content delivery, is that all? Or > you really have some specific pages that are slower than they should? We are not there yet. > > > Hope this helps. > > Sure, I was hoping you found a combination of things that causes Agilo > to slow down, that could improve our performance tests. I would look into why agilo is interfering with delivery of static content. Maybe that will give you some clue on improving the performance. Specifically the requests take a long time to return 304 Not modified HTTP response when agilo is enabled. > > Thanks for your effort, we will make sure to put this information in > the configuration How-To You are welcome. At least now I am at a state where I can try to use agilo in our environment. Thank you very much for agilo and also for your responses. > > Best > ANdreaT --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Agilo for Scrum" group. This group is moderated by agile42 GmbH http://www.agile42.com and is focused in supporting Agilo for Scrum users. 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/agilo?hl=en -~----------~----~----~----~------~----~------~--~---
