LiteSpeed Technologies
Download Download     Blog Blog     Wiki Wiki     Forum Forum     Store     Contact Contact    

Go Back   LiteSpeed Support Forums > LiteSpeed Web Server > LiteSpeed Cache > Litespeed static file benchmarks - Part 1

 
 
Thread Tools Display Modes
Prev Previous Post   Next Post Next
  #1  
Old 01-22-2011, 11:28 AM
eva2000 eva2000 is offline
Senior Member
 
Join Date: Dec 2004
Location: Brisbane, Australia
Posts: 142
Talking Litespeed static file benchmarks - Part 1

My inner benchmark demon took over and got a bit side tracked from testing out Litespeed's inbuilt cache feature. LOL

I ran these static test.txt file apachebench benchmarks to rule out an a possible server config/environment issue which showed up in cache testing in cache tests part 2 - particularly was alot worse with nginx for test.php tests like apache with test.php file details.

Even with static test.txt file, repeated back to back apachebench runs resulted in lower requests per second for apache. While NginX didn't exhibit as bad a result compared to it's test.php tests (2nd run already down to 330 rps). Litespeed seemed immune to dramatic drops at least.

Note:
  1. CPU and Memory utilisation were much higher for Apache than NginX than Litespeed. For example, by 5th ran on 1000 concurrency level, Apache cpu load was hitting 2.8, NginX was around 1.2, and Litespeed around 0.6.
  2. test.txt file used contents was ascii art.
  3. NginX set to 2 workers to compare to 2 cpu Litespeed license
  4. Raw apachebench numbers available here


Last edited by eva2000; 01-22-2011 at 11:34 AM..
Reply With Quote
 

Tags
apache, apachebench, benchmarks, litespeed, nginx

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -7. The time now is 08:38 PM.



- Archive - Top
© Copyright 2003-2011 LiteSpeed Technologies, Inc. All rights reserved. Privacy Policy.