Apache slower than IIS?

[soja92]

Hello,
first off i love xampp, it is the easiest way to setup apache/php/mysql and i love it.

I have xampp hosting a website on a vps, and it is more than capable of serving files at fast speeds, however it seems apache is limiting the servers upload speed somehow.

If i download a file via FTP i download at around 1.4MB/s, but if i download the same file right after through http i only get 300KB/s.

I have tested this on multiple connections, and everywhere its the same result.

If more than one person downloads at the same time it will upload all it needs to, but at a max of around 300KB/s per client (overall it uploads at 3MB/s if needed).

IIS also serves the files at a much higher speed than apache using the same port.

Please help, i have everything setup on the apache server and i don't want to deal with mime types in IIS

Server Config:
Windows Server 2003
Intel Xeon 1.6Ghz Quad-Core hyperthreaded (8 threads in total)
1GB Ram
Xampp version 1.7.2
Apache Version 2.2.12


If you need any other info please let me know!

[soja92]

Really? nobody has any idea?

[soja92]

I apologize for bumping this again, but nobody has any ideas?

[Izzy]

Enable one of the following lines in the file "\xampp\apache\conf\httpd.conf":

Code: Select all

#EnableSendfile off
#EnableMMAP off

The above from the FAQ regarding images not displaying but this fix can also be applied to many strange issues.
http://www.apachefriends.org/en/faq-xam ... netlimiter

Both currently commented out, try removing the comment then save and restart Apache.

[soja92]

Just tried enabling both, and 1 at a time, no change

[Izzy]

XAMPP is pre-configured so it will effectively perform in a development environment even on a PC with low resources.



Before editing any conf or ini file first make a Copy of or backup of the original so you can always revert to the backup for a clean fresh start again.

Not absolutely sure if this will help but you may be able to tune Apache performance in the \xampp\apache\conf\extra\httpd-default.conf file initially by increasing the MaxKeepAliveRequests value to say 500 or more, even to 0 for unlimited.

There may well be other tweaks in this conf files that could help, trial and error is usually the only course open to most of us - try reducing the KeepAliveTimeout to 2 for example.

The other configuration file that may help with performance tuning is the httpd-mpm.conf file - Multi-Processing Modules.

The Multi-Processing Module (MPM) enables a specific platform to handle multiple concurrent connections. MPM modules are platform specific - Unix, Windows, BeOS, and NetWare - for most users the defaults for a particular platform work fine.

This file is governed by <modules> so look out for the module that applies to your platform for example # WinNT MPM - trial and error applies here.
This docs link shows the WinNT MPM and the directives that can be used here:
http://httpd.apache.org/docs/2.2/mod/mpm_winnt.html

This web search (link) may also help.

Remember that if you make changes to any conf or ini file you must save the file and then restart Apache to test again.



Here is a link to a performance tuning article that might also help in your case.
http://www.devside.net/articles/apache- ... nce-tuning

You could also do a web search for keywords:
performance tuning apache for windows
or similar.

Some of the core directives can be read here in the Apache documentation:
http://httpd.apache.org/docs/2.2/mod/core.html


This performance tuning subject (topic) is not one I usually partake in as I have no need of performance in a development environment but I see many forum request for support on this issue.

Good luck and keep the forum posted as to your results.
Thanks.