filer*> sysstat -x 1 CP CP Disk FCP iSCSI FCP kB/s iSCSI kB/s time ty util in out in out 54% Tf 92% 183 0 4 145228 0 0 17% : 96% 201 0 5 149234 0 0
|CP Types||CP Phases|
|B – Back to back CPs (CP generated CP)||0 – Initializing|
|b – Deferred back to back CPs (CP generated CP)||n – Processing normal files|
|F – CP caused by full NVLog||s – Processing special files|
|H – CP caused by high water mark||f – Flushing modified data to disk|
|L – CP caused by low water mark||v – Flushing modified superblock to disk|
|S – CP caused by snapshot operation|
|T – CP caused by timer|
|U – CP caused by flush|
|Z – CP caused by internal sync|
|: continuation of CP from previous interval|
|# continuation of CP from previous interval, and the NVLog for the next CP is now full, so that the next CP will be of type B.|
Here are some explanations on the columns of netapp sysstat command.
Cache age : The age in minutes of the oldest read-only blocks in the buffer cache. Data in this column indicates how fast read operations are cycling through system memory; when the filer is reading very large files, buffer cache age will be very low. Also if reads are random, the cache age will be low. If you have a performance problem, where the read performance is poor, this number may indicate you need a larger memory system or analyze the application to reduce the randomness of the workload.
Cache hit : This is the WAFL cache hit rate percentage. This is the percentage of times where WAFL tried to read a data block from disk that and the data was found already cached in memory. A dash in this column indicates that WAFL did not attempt to load any blocks during the measurement interval.
CP Ty : Consistency Point (CP) type is the reason that a CP started in that interval. The CP types are as follows:
- - No CP started during sampling interval (no writes happened to disk at this point of time)
- number Number of CPs started during sampling interval
- B Back to back CPs (CP generated CP) (The filer is having a tough time keeping up with writes)
- b Deferred back to back CPs (CP generated CP) (the back to back condition is getting worse)
- F CP caused by full NVLog (one half of the nvram log was full, and so was flushed)
- H CP caused by high water mark (rare to see this. The filer was at half way full on one side of the nvram logs, so decides to write on disk).
- L CP caused by low water mark
- S CP caused by snapshot operation
- T CP caused by timer (every 10 seconds filer data is flushed to disk)
- U CP caused by flush
- : continuation of CP from previous interval (means, A cp is still going on, during 1 second intervals)
The type character is followed by a second character which indicates the phase of the CP at the end of the sampling interval. If the CP completed during the sampling interval, this second character will be blank. The phases are as follows:
- 0 Initializing
- n Processing normal files
- s Processing special files
- f Flushing modified data to disk
- v Flushing modified superblock to disk
CP util : The Consistency Point (CP) utilization, the % of time spent in a CP. 100% time in CP is a good thing. It means, the amount of time, used out of the cpu, that was dedicated to writing data, 100% of it was used. 75% means, that only 75% of the time allocated to writing data was utilized, which means we wasted 25% of that time. A good CP percentage has to be at or near 100%.
You can use Netapp SIO tool to benchmark netapp systems. SIO is a client-side workload generator that works with any target. It generates I/O load and does basic statistics to see how any type of storage performs under certain conditions.