Community discussions

MikroTik App
 
marcopolo
newbie
Topic Author
Posts: 45
Joined: Wed Feb 03, 2010 7:17 pm

Memory and CPU history graphs

Wed May 19, 2010 1:36 pm

I've a quick question hopefully.

When I view a graph for a device such as a server, is the CPU % refering to the same % as refered to in the task manager performance as I need to monitor CPU/Memory over a period of time?

Thanks,

Mark
 
User avatar
sergejs
MikroTik Support
MikroTik Support
Posts: 6697
Joined: Thu Mar 31, 2005 3:33 pm
Location: Riga, Latvia
Contact:

Re: Memory and CPU history graphs

Wed May 19, 2010 2:55 pm

Task Manager is showing you live CPU load, however CPU history graph will show you averaged value (sometimes values could be different).
 
marcopolo
newbie
Topic Author
Posts: 45
Joined: Wed Feb 03, 2010 7:17 pm

Re: Memory and CPU history graphs

Wed May 19, 2010 3:21 pm

Thanks, and the % is based on availability, not used
 
User avatar
sergejs
MikroTik Support
MikroTik Support
Posts: 6697
Joined: Thu Mar 31, 2005 3:33 pm
Location: Riga, Latvia
Contact:

Re: Memory and CPU history graphs

Wed May 19, 2010 3:39 pm

Graphs are showing used CPU %.
 
lebowski
Forum Guru
Forum Guru
Posts: 1619
Joined: Wed Aug 27, 2008 5:17 pm

Re: Memory and CPU history graphs

Wed May 19, 2010 4:13 pm

To add to what Sergejs said... the task manager in windows CPU is measured every couple seconds (you can adjust the update speed in the menu).

In the dude it reads the oid every 30 seconds(if you are using the default). So the graph will be similar but not exactly the same as task manager... The cpu could spike for 20 seconds between each each read and you would not notice the spike.

You really do not want the dude trying to poll anything every few seconds unless you are just doing some testing.

Also some devices (Cisco) contain multiple CPU counters. The 3 OIDs in a Cisco are for 5 minute 1 minute and 5 second average CPU.
If you are collecting every 30 seconds on a the 5 minute average OID you will not get a very accurate picture of the CPU.

It depends what you are trying to know over time... You can find some surprising stuff out. Like this Cisco box has some problem where the CPU climbs very slowly. You can see where it failed over to the 2nd supervisor back in March and it is climbing again...
ciscocpu.png
You do not have the required permissions to view the files attached to this post.