+ Reply to Thread
Results 1 to 4 of 4

Thread: Safe Zone

  1. #1
    xaurav's Avatar
    xaurav is offline Almighty
    Join Date
    Mar 2008
    Posts
    105
    WHB Points this Month
    0.00
    WHB Points
    0.00
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Default Safe Zone

    Hi WHBians!!

    I have this curiosity

    What is a safe level for your server load on Shared Hosting.

    Url: http:yoursite.com//:2082/frontend/x3/status.html
    Syntax
    Server Load X.XX (X cpus)

    Example
    Server Load 0.87 (4 cpus)

    This is what we can see in our Cpanel.

    I want to know what people from WHB says about it?

    also,is it also a shared load , or individual load?

    Just a question

    Regards
    Xaurav

  2. #2
    Taras O. Guest

    Default

    Hi Xaurav,

    It is the load of entire server, the optimal load value is number of CPUs + 1. In this case each CPU core is serving one process and 1 process is queued. If the value is higher, it might cause some slowdown, however, in most cases it is not noticeable for human. If the load is less than that value, this means some cores are idle, and consequently there is nothing to worry about.

    We are using Nagios monitoring system, so in most cases we are able to avoid overload cases as it shows alerts when value of CPU load heightened. Also there are other checks, as available disk space, ping stats etc. So, unless CPU load is snowballing, we can prevent overload issues. Otherwise a reboot might be required.

  3. #3
    xaurav's Avatar
    xaurav is offline Almighty
    Join Date
    Mar 2008
    Posts
    105
    WHB Points this Month
    0.00
    WHB Points
    0.00
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Default

    Thanks for Swift reply!!

    Some times having multiple domains ,makes me worried about server load.

    Also i have seen in some other hostings there is "process killing "option.

    I guess its not coupled with shared host.


    Thanks again

    Regards
    xaurav

  4. #4
    Taras O. Guest

    Default

    You can kill processes which were started by you using SSH, i.e. you should be owner of the process. Not sure if it corresponds to what "other hostings" mean by "process killing", but that is what is doable with our hosting.

    Also I can say that our engineers kill processes that are hanged on or consume a lot of system resources. It is a part of our monitoring policy.

+ Reply to Thread

Tags for this Thread

Posting Permissions

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