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

Go Back   LiteSpeed Support Forums > LiteSpeed Web Server > Feedback/Feature Requests > Benchmark

Reply
 
Thread Tools Display Modes
  #31  
Old 05-08-2006, 02:23 PM
Nope Nope is offline
Member
 
Join Date: Mar 2005
Location: Germany/Bavaria
Posts: 11
Well, ok then.

Have you had the chance to take a closer look at my baby then? A couple of features might be overkill for a mere static content server I guess, but it's to be the core of the "real" thing later on.
Reply With Quote
  #32  
Old 05-09-2006, 09:51 PM
BuhBompus BuhBompus is offline
New Member
 
Join Date: May 2006
Posts: 9
OK.. Just for you stat freaks out there, I "tried" to run a benchmark on LiteSpeed/2.1.15 standard vs hssTVS for static content. My results are below..

Notice to LiteSpeed Tech: Your server would not let me run the benchmark as it would only get to "Completed 10000 requests" in ApacheBench and stop. From what I can tell, the log files didn't give me any info, but I think even though I had all the security/throttle/banning options turned off, it was still banning the IP address from any further connections and wouldn't allow anything else from the IP until I restarted the server. Accessing the page using an alternate IP was successful.

Here are the results:

----
ApacheBench 2.0.40-dev
ab -k -n 100000 -c 100 http://127.0.0.1:65000/<numbytes>.html
Notice: Due to the lack of a private network,
these results are LOW due to the fact AB was running on the same machine as the web servers, 127.0.0.1 <-> 127.0.0.1 , therefore CPU usage was VERY effected. These results should be higher if ran across a network using 2 seperate PC's.
----

^^^^^
LiteSpeed/2.1.15 Standard
- 127.0.0.1 - No Logging - Follow Symbolic - Disable Script - Not Restrained - epoll()
- Max KeepAlive: 500 - Smart KeepAlive - No Security - No .htaccess - No Expires

Results:
100 Concurrent: Decided to stop responding to requests even though security was disabled?
Unable to test...
^^^^^^

^^^^^^
hssTVS 0.218d
- 127.0.0.1 - No Logging - 100 concurrent keepalive

100 byte static file: Requests per second: 9889.81
1000 byte static file: Requests per second: 9834.88
4000 byte static file: Requests per second: 8854.65
- Transfer rate: 36434.78 [Kbytes/sec]
16000 byte static file: Requests per second: 5404.62
- Transfer rate: 85601.56 [Kbytes/sec]
^^^^^^

I would be more than happy to run more benchmarks once I get LiteSpeed to work without banning the IP from what it seems like a LOT of connections at a time (even thought it is set to off). I would also like to run the test between 2 seperate PC's on a LAN so I can get real results.

Aaron
Reply With Quote
  #33  
Old 05-09-2006, 11:54 PM
Nope Nope is offline
Member
 
Join Date: Mar 2005
Location: Germany/Bavaria
Posts: 11
Well, you should always include more information about the used system. So Processor/Ram (amount+speed)/hdd (type/size/speed) are the minimum. The OS including distro and exact kernel version, which runlevel and perhaps other demons/programs which may influence the results. If you use a real network it's often of interest which cards/chipsets/switches you've used.

Beside of that, ab in version 2.0.x is not very good. Better would be the older 1.3.x or, for some tests, httperf (also free and together with autobench really convenient). The local loopback is also not so good, but as long as all contestants run on the same machine it can give at least give a clue about the effectiveness. Sadly it ignores network specific things which can have a huge influence on the real world speed of a server program. In case you want to test huge files over a network you might have to start including the CPU usage as then the connection will be most likely the bottleneck.

If ab stops dead after a few thousand requests, check the number of not completely closed sockets. Might be that LiteSpeed uses something like a linger setting which might be bad in such a local loop test scenario. Then you'd have to run multiple tests with only 10000 (or whatever still works) and compare the averages for the contestants.
Reply With Quote
  #34  
Old 08-02-2006, 01:21 PM
zellster zellster is offline
Senior Member
 
Join Date: Sep 2004
Posts: 55
Default Rock Web Server

I would be interested in any benchmarks that compare LiteSpeed and Accoria's Rock web server: http://www.accoria.com/cgi-bin/load?...20Web%20Server

Does anyone have any experience or feedback on this product?
Reply With Quote
  #35  
Old 08-03-2006, 06:37 AM
mistwang mistwang is offline
LiteSpeed Staff
 
Join Date: May 2003
Location: New Jersey
Posts: 7,583
Interesting product. :-)
Benchmarked it a little bit, LiteSpeed Enterprise is about 15%-30% faster than Rock on a simple small static file test, for both non-keepalive and keepalive.
Reply With Quote
  #36  
Old 03-23-2010, 03:00 AM
MindTooth MindTooth is offline
Member
 
Join Date: Apr 2008
Posts: 41
I know this is an old thread, but better to use this one already.

Please include a benchmark of Cherokee Web Server as well. Just tried it, and it works great. Easy to set up PHP.
Reply With Quote
  #37  
Old 03-23-2010, 03:30 AM
NiteWave NiteWave is online now
LiteSpeed Staff
 
Join Date: Sep 2009
Posts: 2,216
FYI -- there are some recent benchmark results in our blog.
Reply With Quote
  #38  
Old 03-25-2010, 02:00 AM
MindTooth MindTooth is offline
Member
 
Join Date: Apr 2008
Posts: 41
None that inculdes Cherokee. But thanks for the heads-up.
Reply With Quote
Reply

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

Similar Threads
Thread Thread Starter Forum Replies Last Post
Benchmark Test Feedback/Feature Requests 7 06-27-2005 08:54 PM
Benchmark andy Feedback/Feature Requests 1 02-04-2004 09:06 PM


All times are GMT -7. The time now is 08:28 AM.



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