I have the following default chart in zabbix, but I have no idea how to interprete these values. Can anyone explain?
-
1A high number of context switches per second generally suggests that multiple threads are competing for shared resources.500 - Internal Server Error– 500 - Internal Server Error2015-08-24 15:12:35 +00:00Commented Aug 24, 2015 at 15:12
-
What exactly are you running there? If you're analyzing your code behavior, please describe what it does. Otherwise this seems off-topic.Leeor– Leeor2015-08-25 08:39:51 +00:00Commented Aug 25, 2015 at 8:39
-
@Leeor, default chart in zabbix template applied to server.user4779895– user47798952015-08-26 08:12:55 +00:00Commented Aug 26, 2015 at 8:12
Add a comment
|
1 Answer
An OS is a very busy thing, particularly so when you have it doing something (and even when you aren't). And when we are looking at an active enterprise environment, something is always going on. (From Wikipedia: zabbix "is designed to monitor and track the status of various network services, servers, and other network hardware.")
Most of this activity is "bursty", meaning processes are typically quiescent with short periods of intense activity. This is certainly true of any type of network-based activity (e.g. processing PHP requests), but also applies to OS maintenance (e.g. file system maintenance, page reclamation, disk I/O requests). I won’t even get into modern power saving technologies.
If you take a situation where you have a lot of such bursty processes, you get a very irregular and spiky CPU usage plot.
PS As “500 – Internal Server Error” says (love that handle!), the high number of context switches are going to make the situation even worse.
PPS The physics nerd in me just has to mention that this is a very common phenomenon in situations where you have a somewhat large number of bursty events (say particle collisions or atomic decay). Once you get into an extremely large number of such events (think Avogadro’s Number), things smooth out.
