# Timeout: The number of seconds before receives and sends time out
Timeout 300
# KeepAlive: Whether or not to
allow persistent connections (more than
# one request per connection).
Set to "Off" to deactivate.
KeepAlive On
# MaxKeepAliveRequests: The maximum
number of requests to allow
# during a persistent connection.
Set to 0 to allow an unlimited amount.
# We reccomend you leave this
number high, for maximum performance.
MaxKeepAliveRequests 100
# KeepAliveTimeout: Number of seconds to wait for the next request
KeepAliveTimeout 15
# Server-pool size regulation.
Rather than making you guess how many
# server processes you need,
Apache dynamically adapts to the load it
# sees --- that is, it tries
to maintain enough server processes to
# handle the current load, plus
a few spare servers to handle transient
# load spikes (e.g., multiple
simultaneous requests from a single
# Netscape browser).
# It does this by periodically
checking how many servers are waiting
# for a request. If there
are fewer than MinSpareServers, it creates
# a new spare. If there
are more than MaxSpareServers, some of the
# spares die off. These
values are probably OK for most sites ---
MinSpareServers 5
MaxSpareServers 10
# Number of servers to start --- should be a reasonable ballpark figure.
StartServers 5
# Limit on total number of servers
running, i.e., limit on the number
# of clients who can simultaneously
connect --- if this limit is ever
# reached, clients will be LOCKED
OUT, so it should NOT BE SET TOO LOW.
# It is intended mainly as a
brake to keep a runaway server from taking
# Unix with it as it spirals
down...
MaxClients 150
# MaxRequestsPerChild: the number
of requests each child process is
# allowed to process before
the child dies.
# The child will exit so
as to avoid problems after prolonged use when
# Apache (and maybe the
libraries it uses) leak. On most systems, this
# isn't really needed,
but a few (such as Solaris) do have notable leaks
# in the libraries.
MaxRequestsPerChild 30
Las directivas anteriores permiten configurar todo lo referente a timeouts, así como el límite de clientes simultáneamente conectados al servidor.