moving postgres to the same machine as trac fixed it.  i found out
server which hosts most all our companies databases to be bogged
down.  my spring backlog generates in about 2secs now.


On Oct 15, 12:24 am, Felix Schwarz <[email protected]> wrote:
> Am 15.10.2009 03:05, schrieb deno:
>
> > i've make a bunch of changes but it didn't seem to do anything for
> > me.  the new ticket page just took 17 secs to be severed.
>
> If it takes so long to load a simple new ticket page, something is
> *very* wrong and you should not bother trying mod_wsgi and/or trac-admin
> deploy (these might improve speed by a second or two but not 15-16).
>
> I assume that the '17 seconds' is the page shown at the bottom of the
> new ticket page? (This is important because it shows us where to look).
>
> 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)
>
> 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
>
> 3. Create a new environment using sqlite. Is the newticket page still
>     so slow?
>
> fs
>
>  smime.p7s
> 4KViewDownload
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to