topic Re: Measuring SAS and SATA performance, what commands on NetApp cDOT and Linux level respectively in ONTAP Discussions

Measuring SAS and SATA performance, what commands on NetApp cDOT and Linux level respectively

netappmagic — Thu, 05 Jun 2025 04:17:46 GMT

Hello,

To measure SAS and SATA aggregates performance, response time, read, write, for instance, what commands will you use on cDOT and Linux level, respectively, aslo in NFS volumes environment.

By most common ways and provided by native commands.

Thanks!

Re: Measuring SAS and SATA performance, what commands on NetApp cDOT and Linux level respectively

netappmagic — Mon, 18 May 2015 17:07:20 GMT

Anybody please help?

Re: Measuring SAS and SATA performance, what commands on NetApp cDOT and Linux level respectively

hariprak — Wed, 20 May 2015 05:59:15 GMT

Hi,

You can try the below command,

node run <nodename> sysstat

Thanks

Re: Measuring SAS and SATA performance, what commands on NetApp cDOT and Linux level respectively

hariprak — Wed, 20 May 2015 06:04:41 GMT

Also, try this commands,

statistics show -object volume -counter read_latency

statistics show -object volume -counter write_latency

Re: Measuring SAS and SATA performance, what commands on NetApp cDOT and Linux level respectively

deepuj — Wed, 20 May 2015 06:27:19 GMT

Hi,

For NFS volumes (this goes with any volumes, but the counters change), you can use the following in diag mode:

::*> statistics show-periodic -object volume -instance <volume_name> -counter <use_the_following_counters>
nfs_other_latency nfs_other_ops
nfs_protocol_other_latency nfs_protocol_read_latency
nfs_protocol_write_latency nfs_read_data
nfs_read_latency nfs_read_ops
nfs_write_data nfs_write_latency
nfs_write_ops

For aggregate total read and write ops, use the following:

::*> statistics aggregate show

Another helpful command

::*> statistics show-periodic aggregate -instance <aggr_name> -counter <give_counter_name>

Thanks,

Deepu

Re: Measuring SAS and SATA performance, what commands on NetApp cDOT and Linux level respectively

neto — Wed, 20 May 2015 17:26:16 GMT

Hi my friend

This is neto from Brazil

How are you?

For blocks...

Thanks

neto

Re: Measuring SAS and SATA performance, what commands on NetApp cDOT and Linux level respectively

chott — Thu, 21 May 2015 07:05:45 GMT

Hi,

the counters available also depend on the ONTAP (8.1, 8.2, 8.3) version you are using.

What Ontap version are you using?

QoS:

Another useful tool for monitoring performance is QoS on the CLI. (Available from 8.2)

To monitor performance simply create a policy-group:

--> qos policy-group create -policy-group <name> -max-throughput 0-INF

This creates a QoS policy without a limit.

Then apply this policy to the Volume, Vserver, LUN, file you would like to monitor

--> vol modify -vserver <svm_name> -qos-policy-group <name>

and use "qos statistics XXXX show" to monitor latency, throughput and others.

OPM:

To set up regular monitoring I would also recommend looking into OnCommand Performance Manager:

http://mysupport.netapp.com/documentation/productlibrary/index.html?productID=61809

The metrics you are looking for are available in the current version, the next version will bring even ore enhancements.

hope that helps.

cheers chriz

Re: Measuring SAS and SATA performance, what commands on NetApp cDOT and Linux level respectively

netappmagic — Fri, 29 May 2015 18:10:39 GMT

::*> statistics show-periodic aggregate -instance <aggr_name> -counter <give_counter_name>

where can I find the list of counter names?

without specifying the counter name, it will list themall, however, the names are twisted on the screen.

Re: Measuring SAS and SATA performance, what commands on NetApp cDOT and Linux level respectively

jasher — Sat, 30 May 2015 21:48:49 GMT

To truly isolate disk performance between the two types of disk, you must run the same tests on each type. That is pretty obvious, but another thing to consider is that the test should be run once before any measurements are recorded in case the workload for the test is able to be cached. So run it once as a warm-up and then immediately run it on the target aggregates. If the target aggregates are on different nodes, each node should get a warm-up run.

The QoS statsistics will help you isolate latency from the disks themselves. Assign a policy with no limit to the target volume and then go under "qos" - > "statistics" -> latency from disk. Follow Neto's and Chriz Ott's suggestions on looking at IOPS and concentrate on the latency from disk from QoS stats.

Always remember that performance is a combination of throughput and latency. Measuring one without the other is not very useful in most cases.