Results 1 to 4 of 4
  1. #1

    Checking Apache Settings

    Are these okay or should I change something

    Timeout 5
    KeepAlive On
    MaxKeepAliveRequests 100
    KeepAliveTimeout 15
    MinSpareServers 5
    MaxSpareServers 10
    StartServers 5
    MaxClients 160
    MaxRequestsPerChild 0

    I changed to these just now and it seems to be working fine would any of these settings cause trouble on a medium busy server?
    [email protected]
    MSN - [email protected]
    AIM - Badda Bing 0003

  2. #2
    Join Date
    Dec 2002
    Dallas, TX
    Using keep alive can cause your server to spawn a lot of Apache children which may slow you down more during peak times versus turning it off. If you want to keep keep alive on, I would increase your max spare servers to at least 25 so Apache won't constantly be starting and stopping unused processes.

  3. #3
    Join Date
    May 2003
    I would just recommend turning KeepAlive off. That way you save a lot of resources, and there is only a tiny noticable difference in site loading. If you have busy sites, you would probably find a large decrease in cpu usage of apache by turning it off.

  4. #4
    Join Date
    Feb 2004
    For two months I am trying different configurations with various success. It seems that less server load induces more memory usage, so it was a matter of try and fail experience to get the golden mean for my particular hardware. This causes automatic increase of the clients number and memory bottlenecks.

    I have firmly established that keeping the MRpChild lower than 2000 creates much strain on the memory, and in fact doubles its use which - in the case of 512 RAM - brings the mashine to a halt and eventually to a series of failures.

    When using the standard Apache configuration with 150 clients and unlimited (0) MRpC, then the averahe memory usage is 60-65. But the server load may go skyrocket high (I have witnessed 440 and more) - especially when Google is indexing a combined triple cgi-feed included in mySql dynamic pages. This caused the Apache to fail every 3-4 hrs and restart automagicly.

    For the last 24 hours I am trying this optimal configuration for Celeron 2.4/1024 RAM/80GHD:

    Timeout 5
    KeepAlive On
    MaxKeepAliveRequests 200
    KeepAliveTimeout 5
    MinSpareServers 5
    MaxSpareServers 20
    StartServers 5
    MaxClients 300
    MaxRequestsPerChild 5000

    So far excellent results:
    Server Load 0.35 (1 cpu)
    Memory Used 34.2 %
    no Apache failure reported

    I will keep you informed in the next 3 days.
    :: :: :: :: :: ::
    :: VDSP.Net :: Directory of virtual and dedi serv providers by location and price

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts