>> Edit article

			이름
			제목
			패스워드

우선 http서버의 256 connection을 좀 더 늘려주시고[512~600,재컴파일] Web-Server와 DB서버를 분리하심이 좋지 않을까요.. : 지금 제가 운영하는 홈페이지의 서버는 리눅스 입니다. : 알짜 6.0 으로 설치되었구요.... : : 서버환경은.. : 펜티엄 800, 512메가 램 으로 구성되어져 있습니다. : 그리고, idc 에 입주해 있구요... : 아파치, mysql, dns, sendmail 을 가동하고 있습니다. : : 그런데... : 문제가요.... : : 예전에는 하루 접속이 5000 건 이하라서 별 문제가 없었는데... : 요즘 하루에 15000 이상의 사람이 접속을 하는 바람에 서버가 죽어나고 있습니다. : : Mem:        517076    514008      3068    379336      10484    117872 : -/+ buffers/cache:    485652    31424 : Swap:      265064    107140    157924 : : free 를 하면 이정도입니다. : : [root@xxxxxxxxx]# pstree : init-+-atd :      |-automount :      |-crond :      |-httpd---256*[httpd] :      |-inetd---ipop3d :      |-kflushd :      |-klogd :      |-kpiod :      |-kswapd :      |-kupdate :      |-mdrecoveryd :      |-6*[mingetty] :      |-named :      |-portmap :      |-proftpd :      |-ras2xm :      |-safe_mysqld---mysqld---mysqld---250*[mysqld] :      |-sendmail---sendmail---procmail :      |-sshd-+-sshd---bash :      |      `-sshd---bash---su---bash---pstree :      |-syslogd :      `-xfs : : 홈페이지 메인뜨는데 1분 2분 이상이 걸리고 있습니다... : : http.conf 의 설정은.... : : # : # Timeout: The number of seconds before receives and sends time out. : # : Timeout 120 : : # : # 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 100 : : # : # KeepAliveTimeout: Number of seconds to wait for the next request from the : # same client on the same connection. : # : 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.  The default values are probably OK for most sites. : # : MinSpareServers 5 : MaxSpareServers 20        : : # : # Number of servers to start initially --- 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 : # the system with it as it spirals down... : # : MaxClients 300 : : # : # 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 0 : : : 이렇게 설정되어져 있습니다. : : 제가 알고자 하는것은... : 설정이 잘못되었는지... : 아니면 설정을 바꾸어서 서버가 안정화 될 수 있는지... : 아니면 램을 확충을 해야 하는지.. : 서버를 분리해야 하는지... : : 저에게 조언을 부탁드립니다.. : : 부탁드립니다...--Everybody has blue days

Copyleft 1999-2026 by JSBoard Open Project Theme Designed by IDOO All right reserved