Skip to main content
NetApp Knowledge Base

What does the wafltop output mean and how can it be interpreted?

  1. Last updated
    Dec 24, 2024
  2. Save as PDF
Views:
368
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
perf
Last Updated:
12/24/2024, 4:31:45 PM

Applies to

Answer

  • It tracks utilization of the following resources:
    • CPU
    • Disk I/O
    • Memory
    • NVLOG utilization
  • The format of the volume name will be: aggregate:volume:protocol:message in the output
Output Meaning
aggregate The name of the Aggregate the Volume resides in
<aggregate>:volume The FlexVol being worked on
<aggregate>:<volume>:
cifs|nfsv3|nfsv4|scsi

Frontend CIFS, FCP, iSCSI, or NFS, or backend protocols like spinvfs, dense, walloc, zombie, or other
<aggregate>:<volume>:
<protocol>:
walloc		 Write allocator
<aggregate>:<volume>:
<protocol>:
dense		 Deduplication or storage efficiency
<aggregate>:<volume>:
<protocol>:
zombie		 File deletions
<aggregate>:<volume>:
<protocol>:
other		 A catchall for any other internal operations, such as WAFL scanners
<aggregate>:<volume>:
<protocol>:WAFL_SPINNP_<operation>

Refers to ONTAP 9 protocol workloads, or user traffic

Example: WAFL_SPINNP_READ is used for user reads
<aggregate>:<volume>:
<protocol>:
backdoor

Refers to some internal WAFL operations that may not be classified in other operation types, but are background in nature

Example: A FlexClone is being split
<aggregate>:<volume>:
<protocol>:
file_io		 Refers to anything passing to/from disk
<aggregate>:<volume>:
<protocol>:
<message_name>

An internal WAFL message, but is only meant to be used by NetApp Employees only, but a few are provided below:
<aggregate>:<volume>:
<protocol>:
SHARING*		 refers to deduplication (scheduled/post-process or inline)
*WAFL_SCAN_*
Terminology:
Term Meaning

CPU Utilization
Latency histograms System (internal) and client latency.
Disk I/O operations Reads and writes from disk in MB and in terms of RAID messages.
NVLog utilization
Memory utilization(Debug only)

Shows buffer cache and inode cache usage in terms of MB used.

Note: Not meant to be used for performance troubleshooting, but only by NetApp Engineering.
I/O Utilization I/O utilization refers to the amount of data read or written in MB/s and IOPS.

 

Additional Information

N/A

 

 

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.