Using nmon version 15e on Oracle Enterprise Linux running this in a cron job:
/usr/local/bin/nmon -ft -s 5 -c 17279
This should run every 5 seconds from midnight to 5 seconds before next midnight.
Now when I take this file and run it through nmon_analyzer version 4.6 the timeline is out of order from left to right. I know this was an issue in previous version but it seems to be happening to me in this version. Here is a sample of the row changes in tab ZZZZ:
T0996 1:23:14 01-Nov-15 01:23
T0997 1:23:19 01-Nov-15 01:23
T0998 1:23:24 01-Nov-15 01:23
T0999 1:23:29 01-Nov-15 01:23
T1000 1:23:34 01-Nov-15 01:23
T10000 12:56:14 01-Nov-15 12:56
T10001 12:56:19 01-Nov-15 12:56
T10002 12:56:24 01-Nov-15 12:56
T10003 12:56:29 01-Nov-15 12:56
T10004 12:56:34 01-Nov-15 12:56
T10005 12:56:39 01-Nov-15 12:56
T10006 12:56:44 01-Nov-15 12:56
T10007 12:56:49 01-Nov-15 12:56
T10008 12:56:54 01-Nov-15 12:56
T10009 12:56:59 01-Nov-15 12:56
T1001 1:23:39 01-Nov-15 01:23
T10010 12:57:04 01-Nov-15 12:57
The T99999 value is sorting by ascii character order.
Looking at the actual nmon file itself time is out of order also.
Somehow:
ZZZZ,T1435,01:59:56,01-NOV-2015
comes before:
ZZZZ,T1436,01:00:01,01-NOV-2015
Don't know if this is somehow tied to the analyzer issue or not
Any help with this would be appreciated.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Can you explain how you intend displaying 17 thousand data points on a graph on a screen with say 1500 pixels across?
This is a classing nmon mistake.
You porbable have too much data and Excel will explode any way.
As you have seen nmon allow for 9999 snapshots which is also too many.
You want 5 digit T numbers.
As you have the data already and want to see graphs you could fix this with sed
s/^T/T0/
s/ZZZZ,T/ZZZZ,T0/
Not tested but I think it will help.
Cheers, Nigel
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Using nmon version 15e on Oracle Enterprise Linux running this in a cron job:
/usr/local/bin/nmon -ft -s 5 -c 17279
This should run every 5 seconds from midnight to 5 seconds before next midnight.
Now when I take this file and run it through nmon_analyzer version 4.6 the timeline is out of order from left to right. I know this was an issue in previous version but it seems to be happening to me in this version. Here is a sample of the row changes in tab ZZZZ:
T0996 1:23:14 01-Nov-15 01:23
T0997 1:23:19 01-Nov-15 01:23
T0998 1:23:24 01-Nov-15 01:23
T0999 1:23:29 01-Nov-15 01:23
T1000 1:23:34 01-Nov-15 01:23
T10000 12:56:14 01-Nov-15 12:56
T10001 12:56:19 01-Nov-15 12:56
T10002 12:56:24 01-Nov-15 12:56
T10003 12:56:29 01-Nov-15 12:56
T10004 12:56:34 01-Nov-15 12:56
T10005 12:56:39 01-Nov-15 12:56
T10006 12:56:44 01-Nov-15 12:56
T10007 12:56:49 01-Nov-15 12:56
T10008 12:56:54 01-Nov-15 12:56
T10009 12:56:59 01-Nov-15 12:56
T1001 1:23:39 01-Nov-15 01:23
T10010 12:57:04 01-Nov-15 12:57
The T99999 value is sorting by ascii character order.
Looking at the actual nmon file itself time is out of order also.
Somehow:
ZZZZ,T1435,01:59:56,01-NOV-2015
comes before:
ZZZZ,T1436,01:00:01,01-NOV-2015
Don't know if this is somehow tied to the analyzer issue or not
Any help with this would be appreciated.
Can you explain how you intend displaying 17 thousand data points on a graph on a screen with say 1500 pixels across?
This is a classing nmon mistake.
You porbable have too much data and Excel will explode any way.
As you have seen nmon allow for 9999 snapshots which is also too many.
You want 5 digit T numbers.
As you have the data already and want to see graphs you could fix this with sed
s/^T/T0/
s/ZZZZ,T/ZZZZ,T0/
Not tested but I think it will help.
Cheers, Nigel