On 8 May, 2009, at 1:17 , Meir wrote:

Hi Meir,

> I've setup a release backlog and that should be helpful, but it's not
> going to solve the problem. I have about 210 items in the backlog and
> they are mostly requirements. This is going to grow quickly as we
> start to hash out User Stories. With about 210 items it's taking about
> 20 seconds. It's running PostgreSQL, mod_python, and apache. Any idea?
> For comparison, the trac "Active Tickets" report loads in 4 seconds.
Wow... a Release Backlog with 210 items... this is how much we do in a  
couple of years :-) Do you have 20 teams working on the backlog?

Jokes apart...

The Active tickets of Trac, loads faster because it just loads summary  
and ids, and it is a flat list... the Agilo Backlog is a bit more  
complex, and it is not only a report, it is an "Active" site where you  
can perform actions and change ticket dependencies. Moreover it is an  
Editable page... and every ticket need to be checked against the  
owner, and we have to build a tree :-)

We are aware of some performance issues, that are extremely bad in  
your case... we have as of now a very short backlog online (61 Items)  
but it loads in 0.61 sec. so I know that probably with 200 or 300  
which are the number we use to make performance tests, we are below  
the 6 sec. so 20 is way far from being optimal... There is a great  
improvement with Item caching in trac since 0.11.2.1, which version do  
you use? Do you have a 'forced' proxy on your network? Which version  
of python are you using?

> Thanks,
YAW

> Meir
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to