Chapter 3 Statistics and Datasets
Determining the impact of a dynamic statistic
Capacity: Capacity Percent Used
Capacity System Pool Bytes Used
Capacity: System Pool Bytes Used
Capacity System Pool Percent Used
Capacity: System Pool Percent Used
Data Movement NDMP Bytes Statistics
Data Movement: NDMP Bytes Statistics
Data Movement NDMP Operations Statistics
Data Movement: NDMP Operations Statistics
Data Movement Replication Bytes
Data Movement: Replication Bytes
Data Movement Replication Operations
Data Movement: Replication Operations
Data Movement Shadow Migration Bytes
Data Movement: Shadow Migration Bytes
Data Movement Shadow Migration Ops
Data Movement: Shadow Migration Ops
Data Movement Shadow Migration Requests
Data Movement: Shadow Migration Requests
Protocol Fibre Channel Operations
Protocol: Fibre Channel Operations
Protocol: HTTP/WebDAV Requests
Data Movement NDMP Bytes Transferred to/from Disk
Data Movement: NDMP Bytes Transferred to/from Disk
Data Movement NDMP Bytes Transferred to/from Tape
Data Movement: NDMP Bytes Transferred to/from Tape
Data Movement NDMP File System Operations
Data Movement: NDMP File System Operations
Data Movement Replication Latencies
Data Movement: Replication Latencies
Disk ZFS Logical I/O Operations
Disk: ZFS Logical I/O Operations
Memory Kernel Memory Lost to Fragmentation
Memory: Kernel Memory Lost to Fragmentation
This statistic shows NFSv bytes/sec transferred between NFS clients and the appliance. Supported NFS in Oracle ZFS Storage Appliance Administration Guide versions are: NFSv2, NFSv3, and NFSv4. Bytes statistics can be broken down by: operation, client, file name, share, and project.
NFSv bytes/sec can be used as an indication of NFS load. The best way to improve performance is to eliminate unnecessary work, which may be identified through the client and filename breakdowns, and the filename hierarchy view. It is best to enable these breakdowns for short periods only: the by-filename breakdown can be one of the most expensive in terms of storage and execution overhead, and may not be suitable to leave enabled permanently on a busy production server.
|
These breakdowns can be combined to produce powerful statistics. For example:
"Protocol: NFSv3 bytes per second for client 'phobos.sf.fishpong.com' broken down by file name" (to view what files a particular client is accessing)
See Network: Device bytes for a measure of network throughput caused by the NFS activity; Cache: ARC accesses to learn how well an NFS read workload is returning from cache; and Disk: I/O operations for the back-end disk I/O caused.