I don't know the exact details, but it's connected to resource allocation. You want the storage system to always respond promptly, and there's code in CVO that makes sure that it's already ready to run and response promptly to IO. A side-effect is that the dashboard thinks the CPU is always busy. It's not really busy, it's just ready to be busy.
You'll need to use the native NetApp monitoring tools to know the actual CPU utilization.
-----Original Message----- From: SE s.eno@me.com Sent: Monday, March 4, 2019 1:35 PM To: Toasters toasters@teaparty.net Subject: Azure CVO and CPU
Hi,
Is anyone here using Cloud Volumes ONTAP in Azure? I’m trying to figure out why it is the Azure dashboard claims our CVO instance is always running at 100% CPU, but if one ssh’s to the virtual appliance and does a sysstat -m on the node it shows all cpus at 0%-1%. Any ideas on the discrepancy between what Azure sees and what ONTAP claims?
— Scott