nmon analyzer 3.5e
Feb 14 | Tags: none
Hi
I made a lot of changes to nmon analyzer in order to update it to increase data size limits and wanted to notify you here in order for desired parties to test before Nigel releases it to everyone. If you want to read about Excel's latest data size limits you can go here:
https://support.office.com/en-nz/article/Excel-specifications-and-limits-1672b34d-7043-467e-8e27-269d656771c3
This was developed with Excel 2013 64-bit, so hopefully it still works OK with Excel 2007 (or older versions with the required MS updates.)
So if you encounter bugs you can either let me know here or at mccargar@us.ibm.com
The changes are:
1. Made changes to increase the ability to handle files with large amounts of data (both rows or columns)
2. Max rows has increased from 65536 to 1048576
3. Max columns has increased from 255 to 16684. This mostly applies to NPIV and SEALICTRAFFIC sheets. The actual number of possible columns would be much less than this (probably < 2000) because of #5. Also note that the DISK tabs still have a hard limit of 255 columns due to the way it is currently coded.
4. Please Note: This increase will also slow down the parsing time and memory requirements considerably in some cases. Previously data was simply truncated at 255 columns.
5. Max size allowed for any line of nmon import data is now 32K.
6. NPIV header was incorrectly shown at the bottom of the sheet previously.
7. NPIV and SEALICTRAFFIC sheets will no longer show any graphs (due to potential huge size which causes the graphs to fail.)
8. Changed the check for EMC to include 'hdiskpower', 'emcpower' or simply 'power'
Please note that with large data sets (> 10 MB or > 1000 columns on any line) you most likely will require 64-bit Windows and Excel and a minimum of 8 GB of RAM.
Also I noticed that the NPIV data I have seen so far seems very strange, all 0s and 17s and the same values on every single line. Does anyone have NPIV data that varies over time? I would like to see it if you do.
