Pootle 2 runs much faster than previous versions, but you can probably still do a few things to improve performance. With a few extra steps, you can support more users and more data. Here are some tips for performance tuning on your Pootle installation.
sqlite3 Pootle/dbs/stats.db "VACUUM;"
For Apache, review your server settings so that you don't support too many or too few clients. Supporting too many clients increase memory usage, and can actually reduce performance.
No specific settings can be recommended, since this depends heavily on your users, your files, and your hardware. However the default value for the
MaxClient directive (usually 256) is almost always too high. Experiment with values between 10 and 80.
If using MySQL backend, for smaller installations it is suggested to go with MyISAM backend (which might result in smaller memory usage and better performance). If high concurrency is expected, InnoDB is suggested to avoid locking issues.
Some templates, especially the front page, require lots of processing for displaying the detailed statistics. You could change how the page is generated to avoid some of that load. Since this page and the statistics should be cached for non-logged in users, most installations would probably not need to look into this. Talk to one of the developers about ways in which to improve this if you are interested.
If you want better performance for your PO based operations, you can try to enable the fast new PO implementation available since Translate Toolkit 1.5.0. This implementation will be used if
USECPO=2 is available in the operating system environment variables. Note that this is different from the Apache environment variables.
Your PO files will have to have character encodings specified, and be perfectly valid PO files (no duplicate messages or other format errors). Be sure to test this extensively before you migrate your live server to this setup.