Forum OpenACS Q&A: Tuning

Collapse
Posted by Steve Manning on
Hi All,

I spent a couple of hours (very) early this morning laying siege (http://www.joedog.org/JoeDog/Siege) to one of our customers production servers to get a better feel for its performance limits. The machine in question is a Dual Xeon 3.2Ghz 64bit (although running 32bit currently) with 4Gb RAM and 72Gb SATA RAID drives.

The results appear to be that it max's out at around 23,000 requests/5 min of testing - about 4,600/min. Looking at the Analog results it appears to be approaching these levels and its peaking at about 80% at the moment so I'm looking for suggestions on tuning the box:

1. Maxconnections is 160 (up from 80) and Threads is 40 (up from a conservative 20). Would increasing these any further be detrimental or is that an unknown (suck it and see)?

2. I notice the default config for 5.1 which it uses does not include any caching for ADP's or FastPath as per this page http://panoptic.com/wiki/aolserver/AOLserver_Tuning%2C_Troubleshooting_and_Scaling

I realise that its a bit old but I'm wondering if there is a reason why I can't use them. Given that we are serving around 80 - 100 requests/page I think that cache of static files such as images would help.

3. Is there a definitive document for Postgres tuning for OACS. There are plenty of documents available on PG tuning but they often seem to contradict each other.

Any thoughts and suggestions would be appreciated.

TIA

- Steve