> 1. Check that your DB server is reasonably fast (don't forget to check > that it is fast to connect to the server if it's on an external machine)
this could be it. our db server is on the other side of a 54Mbps WAN link. i would hope that i didn't need to db on the same local LAN. > > 2. Check for endless Agilo restarts: We had a bug once that Agilo > reloaded itself for every request when run with mod_python. This bug is > fixed in your version of Agilo but maybe we overlooked something. > - Enable debug logging > - restart Apache > - Go to any Agilo/trac page > - check the trac.log, it should contains like > 'DEBUG: Loading trac.mimeview.patch from' > - check that this line is only shown once i don't think this is happening as i upgraded to mod_wsgi yesterday. i just see a lot of 2009-10-15 09:24:12,159 Trac[log] WARNING: [CommandParser] [By Key]: Warning 'allowed_links' 2009-10-15 09:24:12,159 Trac[log] WARNING: [CommandParser] [By Key]: Warning 'source' 2009-10-15 09:24:12,160 Trac[log] WARNING: [CommandParser] [By Key]: Warning 'ticket_types' 2009-10-15 09:24:12,160 Trac[log] WARNING: [CommandParser] [By Key]: Warning 'target' > > 3. Create a new environment using sqlite. Is the newticket page still > so slow? i'll try that. --~--~---------~--~----~------------~-------~--~----~ Follow Agilo on Twitter: http://twitter.com/agiloforscrum ----- 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 -~----------~----~----~----~------~----~------~--~---
