아파치 httpd.conf 현재 기본설정

각 항목 설명이야 찾아보면 나오고

이건 메모리 2G 하루에 만오천명 정도 오는 서버다.

10~11시, 2~4시 사이에 접속이 몰리는 상황.

 

#
# 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 recommend you leave this number high, for maximum performance.
#
MaxKeepAliveRequests 1000

#
# KeepAliveTimeout: Number of seconds to wait for the next request from the
# same client on the same connection.
#
KeepAliveTimeout 2

  2초 : 변경 이걸 최대한 줄여준다 ㅋㅋㅋㅋ

안그러면 지일 끝내고 타임아웃 시간까지 노는 놈들이 많아진다.

#
# 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.  The default values are probably OK for most sites.
#
MinSpareServers 20
MaxSpareServers 40

애네는 별 다른 -_-;;

#
# Number of servers to start initially --- should be a reasonable ballpark
# figure.
#
StartServers 20

#
# 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
# the system with it as it spirals down...
#
MaxClients 840

  이걸 적당하게 해줘야 한다. 메모리 봐가면서 너무 적으면 클릭하고 조금 있다 나타는 버벅거림, 너무 높으면 메모리가 부족해서 서버가 나죽네 한다 

#
# 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 1000