Web Hosting Talk : Web Hosting Main Forums : Hosting Security and Technology : Benchmark result : Lighttpd vs Apache 1.3.36 vs Apache 2.2.2

[goolex]

HardWare : AMD 64 3000+ , 1 GIG RAM
OS : Centos 4.3 32bit
Kernel : 2.6.17

Web Servers
Lighttpd 1.4.11 : php 4.4.2 ( fastcgi ) + eaccelerator
Apache 1.3.36 : php 4.4.2 + eaccelerator
Apache 2.2.2 : php 4.4.2 + eaccelerator

Tests :
1.jpg 80 KB
1.tar.gz 2.5MB
hello.php , simple hello world script

PHP Code:

ab -n 10000 -c 10 127.0.0.1/1.jpg

Lighttpd
Requests per second:    5211.05 [#/sec] (mean)

Apache 1.3.36
Requests per second:    2220 [#/sec] (mean)

Apache 2.2.2
Requests per second:    3883.50 [#/sec] (mean) 


PHP Code:

ab -n 10000 -c 10 127.0.0.1/1.tar.gz

Lighttpd
Requests per second:    357.05 [#/sec] (mean)

Apache 1.3.36
Requests per second:    149.23 [#/sec] (mean)

Apache 2.2.2
Requests per second:    375.02 [#/sec] (mean) 


PHP Code:

ab -n 10000 -c 10 127.0.0.1/hello.php

Lighttpd
Requests per second:    2474.63 [#/sec] (mean)

Apache 1.3.36
Requests per second:    2946.10 [#/sec] (mean)

Apache 2.2.2
Requests per second:    3657.64 [#/sec] (mean) 


[mouseattack]

LOL fudge, power to you brother, tHANK you for that....

if you had tested apache 2.0.58, your tests would have been 100% complete!!!! and then it would be truely even better, but thanks for this!

[goolex]

Originally Posted by mouseattack

LOL fudge, power to you brother, tHANK you for that....

if you had tested apache 2.0.58, your tests would have been 100% complete!!!! and then it would be truely even better, but thanks for this!

done

PHP Code:

Apache 2.0.58

1.jpg
Requests per second:    3590.66 [#/sec] (mean)

1.tar.gz
Requests per second:    329.61 [#/sec] (mean)

Hello.php
Requests per second:    3029.39 [#/sec] (mean) 


[mouseattack]

YOU ROCK! Thanks so much, I reformatted to include ALL 4 test's done by Goolex.

ab -n 10000 -c 10 127.0.0.1/1.jpg

Lighttpd
Requests per second: 5211.05 [#/sec] (mean)

Apache 1.3.36
Requests per second: 2220 [#/sec] (mean)

Apache 2.0.58
Requests per second: 3590.66 [#/sec] (mean)

Apache 2.2.2
Requests per second: 3883.50 [#/sec] (mean)

ab -n 10000 -c 10 127.0.0.1/1.tar.gz

Lighttpd
Requests per second: 357.05 [#/sec] (mean)

Apache 1.3.36
Requests per second: 149.23 [#/sec] (mean)

Apache 2.0.58
Requests per second: 329.61 [#/sec] (mean)

Apache 2.2.2
Requests per second: 375.02 [#/sec] (mean)

ab -n 10000 -c 10 127.0.0.1/hello.php

Lighttpd
Requests per second: 2474.63 [#/sec] (mean)

Apache 1.3.36
Requests per second: 2946.10 [#/sec] (mean)

Apache 2.0.58
Requests per second: 3029.39 [#/sec] (mean)

Apache 2.2.2
Requests per second: 3657.64 [#/sec] (mean)

[mouseattack]

seems like I see that images do REALLY well served through lighttpd but compared to apache 2.2.2, apache 2.2.2 wins all hands down over everything else by a land slide....

What options did you compile all of these with? bare minimums or included all those include statements I saw when i compiled 2.2.2 on my test machine?

Now what we really need to do is have LIGHTTPD serve images only, and apache 2.2.2 serve php and html and everthign else huh? I'm sure many people have already done this, just haven't shared here yet...

man this sure does make me feel stupid for backing 1.3.36 , lol...

[Steven]

Like I said before, 2.2 rocks.

Now what we really need to do is have LIGHTTPD serve images only, and apache 2.2.2 serve php and html and everthign else huh? I'm sure many people have already done this, just haven't shared here yet...

mod_proxy is what you want.

[mouseattack]

really it's mod proxy that I need?

I was thinking that you just don't add the "addtype" line to the httpd.conf of apache 2.2.2, and then have a virtual entry in lighttpd for the same domain, and ONLY have it answer img requests similar by ONLY having whatever is equivalent to addtype on httpd for .jpg .gif .jpeg .png on lighttpd, and run lighttpd on port 81 instead of port 80 where httpd is running.....

would this work or am I just dreaming agian, which is more efficient?

my friend who knows linux alot better than I, gave me some tips on how to make apache use LESS ram and LESS cpu.....

he told me to recompile ONLY with the most important needed modules, so I recompiled with mod rewrite on apache 1.3.36 ( going to upgrade to 2.2.2 very soon ) and recompiled php 4.4.2 ONLY with curl and mbstring, and that is all, no other flags.

Is he right in this that this is more efficient, instead say if I compiled php with FTP, ming, xml, and gd as well as curl, and recompiled apache with --enable-shared=all , would it be a huge fall pit?

He also informed me to comment all the unneeded apache includes out that i didn't need in efforts of optimization....


example:

cpanel / centos 4.3 / apache 1.3.36

copied from httpd.conf

LoadModule rewrite_module libexec/mod_rewrite.so
#LoadModule expires_module libexec/mod_expires.so
LoadModule php4_module libexec/libphp4.so
#LoadModule bwlimited_module libexec/mod_bwlimited.so
LoadModule bytes_log_module libexec/mod_log_bytes.so
#LoadModule auth_passthrough_module libexec/mod_auth_passthrough.so
LoadModule gzip_module libexec/mod_gzip.so

# Reconstruction of the complete module list from all available modules
# (static and shared ones) to achieve correct module execution order.
# [WHENEVER YOU CHANGE THE LOADMODULE SECTION ABOVE UPDATE THIS, TOO]
ClearModuleList
AddModule mod_env.c
AddModule mod_log_config.c
AddModule mod_mime.c
AddModule mod_negotiation.c
AddModule mod_status.c
AddModule mod_include.c
AddModule mod_autoindex.c
AddModule mod_dir.c
AddModule mod_cgi.c
AddModule mod_asis.c
AddModule mod_imap.c
AddModule mod_actions.c
AddModule mod_userdir.c
AddModule mod_alias.c
AddModule mod_rewrite.c
AddModule mod_access.c
AddModule mod_auth.c
#AddModule mod_expires.c
AddModule mod_so.c
AddModule mod_setenvif.c
<IfDefine SSL>
AddModule mod_ssl.c
</IfDefine>
#AddModule mod_frontpage.c
AddModule mod_php4.c
#AddModule mod_bwlimited.c
AddModule mod_log_bytes.c
#AddModule mod_auth_passthrough.c
AddModule mod_gzip.c

as you can see i commented out anything i didn't know what it was specifically, lol...... loll..............

[Steven]

Addtype line?

I usually proxy images requests to lighttpd from apache.

He is right about it being faster.

Apache 2.2 rocks 1.3 anyday of the week.


./configure --prefix=/usr/local/apache --enable-rewrite --enable-ssl --enable-so

[mouseattack]

lol, man do you love 2.2.2 or do you LOVE 2.2.2 ?

heh... glad he's right, i will continue to comment unneeded lines out lol, if it breaks something, just uncomment

[Steven]

I use apache 2.2 on several large vbulletin forum clusters. Once you got 2.2 you never go back

[layer0]

Steven,

Have you ran 2.2.2 on a cPanel box by any chance? (Or tried running, rather)

[Steven]

Originally Posted by elix

Steven,

Have you ran 2.2.2 on a cPanel box by any chance? (Or tried running, rather)

I have tried, and it "kind of works", however you must hand build the entire configuration file. 2.2 splits it into many files as includes. Regular suexec doesnt work correctly however. If you have time and the energy it can be done.

[mouseattack]

what other optimization did you do for "Several large forums", vb uses mysql, duh, so i'm wondering what a true professional like yourself Steven uses for /etc/my.cnf and any other tweaking in httpd.conf and php.ini for large forums? ( might as well tweak everything while i'm at it) I am working on that kernel upgrade but aside from that it'd be nice to know some kick butt settings for those files, playing the guessing game isn't working too well, and well, lol, who has time to read 1,000+ documentation over ay mysql.org about high performance tweaking.... they should just make the default high performance, that way save everyone some time!

~Mouse

[Steven]

Every cluster is setup to fit the setup, no one size fits all. Depends on the kind of querys

[mouseattack]

ok recompiled kernel yet again, same issue... Will post entire .config in the morning, I did not see the iptable setting anywhere in that .config , but no kernel panic thank god? heh....

~mouse