- under load, apache lock make it slow because of the nature of virtualisation. So threads waits for the lock. And Apache need to launch more processes. If your memory is limited ( 3go under FReeBSD without specific kernel), apache need time to launch new process from disk.
- SSL is a always more CPU dependant.
- clients must do be able to cache data.
Here is my preferences :
AcceptMutex sysvsem
This change the locking scheme for every locks.
Comment any files (Scoreboard, LockFile, REwriteLock...)
SSLMutex sem
use memory, never use disks
CacheNegotiatedDocs On
and configure according to your data (think about varnish/nginx cache)
KeepAlive Off
Don't try to keep alive things. One connection is only required for multiple datas.
KeepAlive let processes wait for nothing.
SSLSessionCache shmcb:/var/run/ssl_scache(512000)
USe cache for SSL with circular bucket in memory
SetEnvIf Request_URI "\.(pdf|flv|jpg|jpeg|png|gif|js|css|gz|swf|txt)$" dontlog
CustomLog /var/log/httpd-ssl_request.log \
"%t %h %{SSL_PROTOCOL}x %{SSL_CIPHER}x \"%r\" %b" env=!dontlog
Don't log unless it's valuable

Aucun commentaire:
Enregistrer un commentaire