-APC cache. I recommend APC cache over eAccelerator if you're not on a shared environment, or need the decoding abilities of Zend Optimizer. If you do, then run eAccelerator (keep an eye out for bugs) + Zend Optimizer.
-Run PHP 5.1.2+. PHP 5 is horribly slow, and I prefer it over PHP 4. By default, PHP 5 also passes objects as references rather than copies which can save on RAM.
-PHP via FastCGI or similar. I run my PHP with Litespeed webserver...it has a custom SAPI module that's faster than FastCGI, but even so FastCGI is far faster than CGI or mod_php.
-Dump Apache. Apache is a great server, but it tries to be everything to everyone and is rather clunky. Use Lighttpd (can use FastCGI), or give Litespeed webserver a try.
-Setup MySQL with a query cache. It takes more RAM, but it saves the need for executing the same SELECT queries over and over when the dataset is still the same.
-Disable per-thread and per-forum "who's online". It's a neat feature, and I use it, but if you're squeezing for performance this can help.
Go to vBulletin.com and visit the server optmization forum.
APC cache is nice, so go with it.
PHP 5 with APC is a great optimization and I'd have to recomend it, altho PHP4 is just as fast overall.
Do not run php as CGI/FastCGI esp if you continue running apache.
Not everyone has the ability to dump apache, possibly cpanel in the way, however you can still make use of lighttpd by compiing it binding it to a free ip and moving your static images over to it on a subdomain like images.domain.com.
The plugin based template cache is not actually that much more of a preformance boost in a large real world enviroment.
Thanks for your responses, the server is mine but the problem is that i pay for plesk panel and plesk need apache.
WRT APC, i test APC a months ago and the load o f my server up and up. eAccelerator ever work well for me. I try use Lightspeed in another server for images only and update to PHP 5.1.
I remove the Raid1 of my server and move MySQL to the secondary disk, now the response is incredible
What about adding new accounts, cpanel tryign to restart apache? etc?
Litespeed automatically reloads the apache config when it changes. As for the rebooting, I just replaced /etc/init.d/httpd with a custom wrapper for lswsctrl. Also, Litespeed when importing Apache config writes out the byte log like Apache would, so bandwidth is still shown. Suspending a site is just a rewrite rule, so that's no problem either. Also, in the latest release of Litespeed you can manually specify a byte log in vhosts you create so you can track bandwidth (either through CPanel or otherwise).
More tips:
-Set CSS to save to file.
-Set attachment and profile/avatar pictures to save to filesystem.
Ways to optimize vBulletin post your solutions Details »»
About Developer
Visit Web Site
No support by the author.
05-09-2006, 06:34 PM
