Skip to main content
NetApp Knowledge Base

What is the "_ocs_vserver" workload in qos statistics?

Views:
216
Visibility:
Public
Votes:
1
Category:
ontap-9
Specialty:
perf
Last Updated:

 

Applies to

ONTAP 9

Answer

  • This may be identified from a Performance case, or from the command qos statistics workload resource cpu show.
  • For example:

cluster1::> qos statistics workload resource cpu show -node nodeB
Workload            ID   CPU
--------------- ------ -----
-total- (100%)       -   30%
_ocs_vserver_a3      -   20%
vs0-wid101         101   12%
file-1-wid121      121   10%
vol0-wid1002      1002    8%
_DEDUP               -    7%
-total- (100%)       -   30%
vs0-wid101         101   12%
file-1-wid121      121   10%
_ocs_vserver_a3      -   10%
vol0-wid1002      1002    8%
_DEDUP               -    7%

  • _ocs_vserver, is a QoS internal workload ID for Copy Offload, known as VAAI, ODX
  • Offloading the reading of data from a source and the writing to a destination via the use of an in-band SCSI command known as "EXTENDED_COPY".
  • This mainly includes Storage V-Motions (vmware initiated data migration)
  • For Copy Offload work, OCS creates a default QoS workload per destination vserver; each workload is associated with the Best Effort policy by default.
  • These workloads follow a well-defined naming scheme; each workload name is of the form _ocs_vserver_<vserver UUID>, where the vserver ID is the UUID of the destination vserver.
  • These workloads are visible through the normal QoS commands as are statistics for those workloads. 
  • By default, OCS workloads will use a Best Effort policy.There is no mechanism provided to increase the level of service for copy offload above the "Best Effort" policy.
  • While the QoS interfaces do not provide the ability to manage those workloads' policies, there is a diag-mode command, copy-offload modify, that can set a throttle on misbehaving copy-offload workloads.
     

 

 

Additional Information

NA