Sorry it took so long to answer, I was on vacation. On Jul 30, 3:59 pm, Robert Buchholz <[email protected]> wrote: > On Thursday 29 July 2010, jmb wrote: > > > On Jul 28, 10:16 am, Robert Buchholz <[email protected]> > > > How many tickets do you have in your sprint? > > > Around 40 to 50 tickets (tasks and user stories, both). > > That's a good backlog. So I'm not sure how to help you. You could try > profiling your python process and see where it hangs, but I have not > seen it take that long myself. > I've run the request through the python profiler (using repoze.profile: http://repoze.org/repoze_components.html). The problematic call stack looks like this:
main.py:315(dispatch_request) main.py:438(_dispatch_request) main.py:140(dispatch) dashboard.py:93(process_request) dashboard.py:64(_add_charts_to_template_data) chart_generator.py:125(get_chartwidget) chart_generator.py:83(_get_widget) resource_assignment_piechart.py:36(generate_widget) resource_assignment_piechart.py:63(populate_with_sprint_data) controller.py:351(process_command) controller.py:306(execute) controller.py:836(_execute) At each step in this stack, the cumulative time is over 23s. Then it gets split between two calls of each about 11s: controller.py:351(process_command) and controller.py:795(get_load_series_for_interval) I'll put the profiler log here: http://jeberger.free.fr/public/trac-profile.log if you want to take a look. > > I've also noticed that if I reload the dashboard immediately, it > > often (but not always) loads much faster (2 to 4 seconds for the > > .../ dashboard request!) > > Probably a sign that file system caching helps alleviate the problem. > How large is your sqlite database (tracenv/db)? > The sqlite database itself is 495K. The trac environment is 3.4M. Jerome -- Follow Agilo on Twitter: http://twitter.com/agiloforscrum Please support us by reviewing and voting on: http://userstories.com/products/8-agilo-for-scrum http://ohloh.net/p/agilo-scrum http://freshmeat.net/projects/agiloforscrum You have received this message because you are subscribed to the "Agilo for Scrum" Google Group. This group is focused on supporting Agilo for Scrum users and is moderated by agile42 GmbH <http://www.agile42.com>. To post to this group, send email to [email protected] To unsubscribe from this group, send an email to [email protected] For more options, visit this group at http://groups.google.com/group/agilo
