![]() |
Litespeed vBulletin index.php benchmarks - Part 1
Just installed vB 3.8.6 PL1 test forum on test server to benchmark Litespeed v4.0.19. Only testing the front vB index.php page first.
Results are very much bottlenecked by MariaDB 5.2.4 MySQL server connection unlike standalone test.php or test.txt static file testing already done. Summary
Apachebench
Quote:
Raw numbers here Server config ran Unixbench 5.1.2 as per http://www.webhostingtalk.com/showthread.php?t=924581 to see how it compares.
Code:
======================================================================== |
With some help from Litespeed folks, got litespeed's inbuilt cache feature setup to work with vBulletin's boost/varnish plugin - basically just import/install product-boostv1.xml on your vB 3.8.x or vB 4.0.x forums and setup Litespeed cache options in Litespeed admin console and drop in some vB specific .htaccess rewrite code and you're set.
The speed boost for guest visitors is crazy - between >16x to 123x times faster in different apachebench config tests! Now to retest apachebench with above same settings for requests and concurrency with Litespeed inbuilt cache enabled resulted in Litespeed inbuilt cached tests being up to 721x times faster than Apache, or 91x times faster than Litespeed alone without the inbuilt cache enabled! :eek: Look at the cpu load for cached tests and no php memory usage at all :) Quote:
Litespeed admin console cache policy and settings * need to create cache path directory /lscache Code:
Cache Storage SettingsCode:
RewriteEngine onfor index.php header via Firefox Firebug addon Code:
Content-Encoding gzipCode:
ls -alhR /lscache |
Torture testing Litespeed Inbuilt cache against vB 3.8.6 PL1 front index.php page with apachebench at:
Try the above with apache and only 1-2GB memory :D Not a single failed request ! 5000 concurrency + 1 million requests Apachebench = 7,846.05 rps - over 240x times apache's performance handling 100x times the number of requests and 25x times the concurrency Code:
ab -k -n 1000000 -c 5000 http://192.168.56.101/index.phpCode:
top - 16:27:02 up 23 min, 3 users, load average: 9.43, 3.15, 1.565000 concurrency + 1.5 million requests Apachebench = 9,151.34 rps - 280x times apache's performance with 150x times number of requests and 25x times the concurrency. Code:
ab -k -n 1500000 -c 5000 http://192.168.56.101/index.phpCode:
top - 17:42:28 up 1:02, 3 users, load average: 2.86, 1.33, 0.50 |
:: Jan 28th, 2011: Correction to findings
I have to revise my findings a bit for Nginx in above tests. The failed requests seem to be from content length varying between apachebench requests and not due to failure requests related to connections/exceptions errors. Content length varies due to dynamic nature of php pages tested as as long as content length reported by apachebench as Document Length is nearly the same, it still means a successfully served request regardless. However, not sure why litespeed did have any of these errors vBulletin index.php page tests. The reason I came across this is because I have been able to implement same litespeed cache method for use on wordpress as well. However, litespeed apachebench testing wordpress pages results in same failed request due to content length varying between requests. So I guess as long as apachebench Document Length is varying only slightly in size, you can ignore the failed requests if they are due to content length as reality is the php page would have been served. Example: testing wordpress page non-cached nginx, litespeed and apache with only apachebench testing 2 requests and 1 concurrent all reported failed request due to content/document length Failed request due to content/document length Code:
Failed requests: 1Code:
ab -k -n 2 -c 1 http://192.168.56.101/wp/?p=1417Code:
ab -k -n 2 -c 1 http://192.168.56.101/wp/?p=1417Code:
ab -k -n 2 -c 1 http://192.168.56.101/wp/?p=1417 |
Very nice Benchmark.
Still can not make Guest Cache working with VBSEO. |
Quote:
I finally managed to get Varnish VCL tuned to work with vBulletin 3.8.6 PL1 as well, so updated the above table to include Apache + Varnish 2.1.5 vB index.php tests to the list as well as update the table column to remove failed requests in the calculation of adjusted rps for nginx. http://vbtechsupport.com/litespeed/b...n28updated.png Looks like when you include mysql backend as a factor in testing vB index.php page, litespeed cache just edges out Apache + Varnish. Unlike, with php based test.php file where Apache + Varnish took the lead - although it seems i hit a litespeed cache memory leak bug in those tests. |
Thank you.
Hope to see VBSEO + Litespeed cache soon. |
Thanks for the nice guide,
i got the cache working, i have a server using haproxy/nginx as load balancer before litespeed webserver. Code:
Server nginxIs there something missing? I am using VBB 3.8.6 Update: I found the problem, it was the .htaccess i copy from your but forgot to edit according to my server: Quote:
|
yeah vb cookie prefix needs setting for your specific forum :)
|
| All times are GMT -7. The time now is 02:18 PM. |