une solution serait de diminuer le nombre d'instance d'apache lancée en même temps..
mais c'est pas une solution qui empechera à un type de faire crouler ton site.
sinon il y a
# KeepAliveTimeout: Number of seconds to wait for the next request from the
# same client on the same connection.
#
KeepAliveTimeout 10
ou encore
#
# 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 memory or other resources. On most systems, this
# isn't really needed, but a few (such as Solaris) do have notable leaks
# in the libraries. For these platforms, set to something like 10000
# or so; a setting of 0 means unlimited.
#
# NOTE: This value does not include keepalive requests after the initial
# request per connection. For example, if a child process handles
# an initial request and 10 subsequent "keptalive" requests, it
# would only count as 1 request towards this limit.
#
MaxRequestsPerChild 100
bon, j'espere que tu comprends l'anglais...
tu recherche sur google ces 2 mots... et tu devrais avoir un complement.
Bonne chance pour resoudre ton problème
---------------
Mon site http://j2c.org