If you specify the -fields <fieldname>, …​ parameter, the command output also includes the specified field or fields. You can use '-fields ?' to display the fields to specify.

If you specify the -instance parameter, the command displays detailed information about all fields.

This parameter specifies the Node name.

This field represents an upper boundary on the allowed put rate. The put rate will not be allowed to exceed this value but can be throttled to values less than it to accommodate client operations and a high average system CPU. Some platforms are intentionally configured with a lower maximum put rate in an effort to reduce the impact of the FabricPool put subsystem on the overall system health. A limit in effect, lower than the default, may keep cold data in the performance tier for a long period of time and may require an increase in space requirements. A value of -1 indicates no upper bound is in effect.

The put-rate displays the maximum computed bytes per second the put subsystem assumes is possible. This put rate is measured in real-time and is in relation to the node for all attached object stores which have put traffic to them.

This field displays the maximum allowed put rate. If it is less than the max-throughput then it indicates that throttling is in effect. The throttling is the outcome of either staying at put-rates-byte-limit or an effort to accomodate client operations on a system with high CPU.

This field displays the maximum put throughput rate in bytes per second that the put subsystem will throttle down from or up to. It's the greater of the put-rate and the node default value.

This field displays the average put latency in milliseconds over the last several seconds to all object stores to which there is put traffic.

This field displays the put latency threshold in miliseconds at which point the number of parallel put operations to all object stores is decreased. The average put latency is displayed in the put-latency field.