2010-08-02 09:51 AM
Someone told me that the Read Latency (msec) in the Performance view is in microseconds and not milliseconds. Is this correct? I always assumed msec was the abbreviation for milliseconds.
Solved! SEE THE SOLUTION
2010-08-03 12:46 AM
Few more information on this thread:
counter unit of "Read Latency" for NFS, CIFS and ISCSI are in milliseconds and for others like I/O memory it is in microseconds.
This is applicable for latest ONTAP version.
2011-05-11 07:49 AM
I about fell out of my chair this morning after upgrading System Manager 1.0 to 1.1 and getting the new Read Latency scale.
6,037 msec in this world is 6,037 milliseconds of latency. And knowing that about seventy VMs including SQL and Exchange clusters are sitting on this... yes, I almost fell out of my chair.
Then, I find that in NetApp World - msec actually means microseconds, but only in this graph on this app.
Seriously guys... please use the Mu so that it reads μsec.
2011-05-12 11:45 PM
We have a public beta going on for SM 2.0. Could you please take a look and provide feedback? Here’s the link to the public beta
2011-07-19 06:40 AM
By all means tell me if I am wrong but having compared the latency figures for CIFS and NFS it appears obvious that someone has coded the graph wrong so that CIFS are showing on the graph in milliseconds whilst NFS is still showing in microseconds.
My guess is that someone applied a division by 1000 to CIFS, etc but not to NFS.
Does anyone at NetApp have access to the code that can check this out. In it's current layout it makes monitoring CIFS from the Systems Manager interface impossible.