=======================================================================================================
1.
Put the cache on a separate diskMove your cache to a separate physical disk for the fastest access without slowing down other processes.
2
.Disable .htaccessI.e. AllowOverride None. This will keep Apache from checking for an .htaccess file upon each request.
3.
Increase Write Buffer SizeIncrease your write buffer size for TCP/IP buffers. On Linux systems increase /proc/sys/net/core/wmem_max and /proc/sys/net/core/wmem_default. If your pages fit within this buffer, Apache will complete a process in just one call to the TCP/IP buffer.
4.
Don‘t use threaded mpm with mod_phpLook at using mod_itk, mod_php tends to segfault with threaded mpm.
5.
Log to a different disk than the disk serving pagesPut your logs on physically different disks than the files you are serving.
6.
Setup appropriate Expires, Etag, and Chache-Control headersIn order to utilize your cache you have to specify when a file expires, otherwise your client will not experience the caching benefits.
7.
Remove unused modulesSave memory by not loading modules that aren’t needed, including (but not limited to)…
… mod_php,
… mod_ruby,
… mod_perl
8.
Setup appropriate Expires, Etag, and Chache-Control headersIn order to utilize your cache you have to specify when a file expires, otherwise your client will not experience the caching benefits.
9.
Turn off HostnameLookupsStop doing effortful DNS lookups. You will rarely ever need them and when you do, you can always look them up when really needed.
10.
Do not set KeepAliveTimeout too highIf you have more requests than Apache children, settings which are set too high could exhaust your pool of available clients.
That's all
=======================================================================================================