Well, have a look at the 'top' output to see if you can identify the process causing high load. If there's nothing obvious, then it's possible that the node itself is overloaded in which case you'd contact the host.
@Romanov007 said:
Well, have a look at the 'top' output to see if you can identify the process causing high load. If there's nothing obvious, then it's possible that the node itself is overloaded in which case you'd contact the host.
It is not the node but about using top , Can I use top any time? or I have to wait when the high load happens again?
@Romanov007 said:
Well, have a look at the 'top' output to see if you can identify the process causing high load. If there's nothing obvious, then it's possible that the node itself is overloaded in which case you'd contact the host.
It is not the node but about using top , Can I use top any time? or I have to wait when the high load happens again?
You might try "atop" instead. It has daemon running in background, periodically logging statistics. It helps in cases when load-peak is short, and dissapears before you notice email and log in to check load interactively...
Comments
Well, have a look at the 'top' output to see if you can identify the process causing high load. If there's nothing obvious, then it's possible that the node itself is overloaded in which case you'd contact the host.
It is not the node but about using top , Can I use top any time? or I have to wait when the high load happens again?
you can top whenever you want
You might try "atop" instead. It has daemon running in background, periodically logging statistics. It helps in cases when load-peak is short, and dissapears before you notice email and log in to check load interactively...