Isn't the simplest option to place a decent reverse proxy between the webserver and our clients?
For example, varnish will cache and proxy simple GETs, so simple views of the front page and docs (which I imagine is a large chunk of the traffic) will be offloaded from the webserver: http://varnish.projects.linpro.no/wiki/VarnishFeatures
Also, is the current installation (Db, apache + trac) all on one machine or are the DB and the webserver split already?
These would be easy ways to throw more hardware at the problem.
What is the current web-server configuration? Can you share traffic stats for the top 20 pages, so we get an idea of where the load is?
From: "ssteinerX@gmail.com" email@example.com Subject: Re: [Twisted-Python] Volunteer for twisted code Reviews and Commits To: Twisted general discussion firstname.lastname@example.org Message-ID: C38535FC-8267-4162-B67C-1F27822CBC8D@gmail.com Content-Type: text/plain; charset=us-ascii; format=flowed; delsp=yes
On Nov 7, 2009, at 8:51 AM, David Lyon wrote:
On Sat, 07 Nov 2009 13:32:28 -0000, email@example.com wrote:
A server farm doesn't buy us anything, as trac can't be scaled up across multiple hosts (or even multiple CPUs on a single host).
I'm surprised to hear that.
Usually replication of servers for read requests works well with dns sharing.
Does Trac not run a database? that can go on another machine and lighten the load.
Anyway, it's your call. Keep up the good work.
I think the best option may just be to collect machine, database, and usage stats and ask the trac guys for help.
Twisted-Python mailing list Twisted-Python@twistedmatrix.com http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
End of Twisted-Python Digest, Vol 68, Issue 12