Red Hat LINUX 7.2 - OFFICIAL LINUX CUSTOMIZATION GUIDE Guida di Installazione Pagina 181

  • Scaricare
  • Aggiungi ai miei manuali
  • Stampa
  • Pagina
    / 282
  • Indice
  • SEGNALIBRI
  • Valutato. / 5. Basato su recensioni clienti
Vedere la pagina 180
Chapter 15. Apache 181
15.3.8. Timeout
Timeout defines, in seconds, the amount of time that your server will wait for receipts and trans-
missions during communications. Specifically, Timeout defines how long your server will wait to
receive a GET request, how long it will wait to receive TCP packets on a POST or PUT request and
how long it will wait between ACKs responding to TCP packets. Timeout is set to 300 seconds,
which is appropriate for most situations.
15.3.9. KeepAlive
KeepAlive sets whether your server will allow more than one request per connection (in other words,
it will allow persistent connections). KeepAlive can be used to prevent any one client from consum-
ing too much of the server’s resources.
By default Keepalive is set to off. If Keepalive is set to on and the server becomes very busy, the
server can quickly spawn the maximum number of child processes. In this situation, the server will
slow down significantly. If Keepalive is enabled, it is a good idea to set the the KeepAliveTimeout low
(see Section 15.3.11) and monitor the servers /var/log/httpd/error_log. This log will report
when the server is running out of child processes.
15.3.10. MaxKeepAliveRequests
This directive sets the maximum number of requests allowed per persistent connection. The Apache
Group recommends a high setting, which will improve your server’s performance. MaxKeepAliv-
eRequests is set to 100 by default, which should be appropriate for most situations.
15.3.11. KeepAliveTimeout
KeepAliveTimeout sets the number of seconds your server will wait after a request has been served
before it closes the connection. Once the server receives a request, the Timeout directive applies
instead.
15.3.12. MinSpareServers and MaxSpareServers
The Apache Web server dynamically adapts to the perceived load by maintaining an appropriate num-
ber of spare server processes based on the traffic. The server checks the number of servers waiting for
a request and kills some if there are more than MaxSpareServers or creates some if the number of
servers is less than MinSpareServers.
Your server’s default MinSpareServers is 5; your server’s default MaxSpareServers is 20. These
default settings should be appropriate in most situations. You should not increase the MinSpare-
Servers to a large number. Doing so will create a heavy processing load on your server even when
traffic is light.
15.3.13. StartServers
StartServers sets how many server processes are created upon startup. Since your Web server
dynamically kills and creates server processes based on traffic load, you will not need to change this
parameter. Your Web server is set to start eight server processes at startup.
Vedere la pagina 180
1 2 ... 176 177 178 179 180 181 182 183 184 185 186 ... 281 282

Commenti su questo manuale

Nessun commento