ebyblog students and information

Posted
19 March 2007 @ 11pm

Tagged
General, code4lib

Trac Performance

In the past I’ve used mod_python to serve trac and got ok performance, but my installs weren’t public. On Code4Lib it was set-up as a fcgi install. This worked ok but was extremely resource intensive.

I also host through TextDrive and found that they recommend running Trac through Tracd and then proxying the requests through apache if you want it on the normal port. I went ahead and tried that on code4lib. Trac seems responsive and the system didn’t go to a crawl while it was being accessed. We’ll see how it does in the long run.

If you run trac you might want to give it a try.


No Comments Yet


There are no comments yet. You could be the first!

Leave a Comment

Bookmarks for March 18th through March 19th Retagging and Changing Logs in SVN