From: Graham D. <Gra...@gm...> - 2009-04-10 10:50:21
|
On Apr 10, 12:25 am, Nick Hughart <mek...@mekius.net> wrote: > On Thu, 9 Apr 2009 07:49:27 +0200 (CEST) > > Vincent Torri <vto...@univ-evry.fr> wrote: > > > Hey, > > > as a lot of us know, we have some problems with trac (password when > > using tickets, lots of cpu consumption, need of removing cookies when > > trying to login, globally very slow, etc...). > > > I have asked in #trac to have some kind of answers and i put the > > quotes in that mail for posterity. > > > 1) about cpu consumption, the answer is: do not use CGI, use anything > > else. The advices were: "FastCGI, mod_python, tracd, ormod_wsgi" > > Tried mod_python once and trac went so out of control that the whole > server locked up and we had to have OSUOSL restart it. The only > solution I think will fit us is fastcgi. I know I researched this > before and all the other solutions had lists of problems associated > with them. I know cgi is slow, but time is money as they say and I > have little of both right now :) Read: http://blog.dscpl.com.au/2009/03/load-spikes-and-excessive-memory-usage.html It will tell you why you had problems with mod_python. Graham |