CPU (in MHz) and CPU Cap

[baltazorbest]

Hello everyone.

I have one suggestion regarding the CPU (in MHz): to hide it from the user if the CPU cap is disabled, because it confuses users when the CPU cap is turned off. If I’m wrong, please let me know and explain why.

Thank you.

[DaanHoogland]

@baltazorbest why would we tie a CPU speed to the cap of that speed? It might still be interesting to see an actual speed even when it can be increased, is it?

[daviftorres]

@baltazorbest , what Hypervisor are you using?

On KVM, CPU allocation is based on weight (time share), not on the CPU frequency.

Since we have clusters with different CPU speeds, we must set compute offerings to match the slowest cluster. Otherwise, deployment fails if a host’s CPU clock is lower than what’s specified.

A “max” option for frequency would solve this, letting clients choose only the number of vCPUs without worrying about clock speed.

[baltazorbest]

@daviftorres Hi, my hypervisor is KVM. Is this max option already available or is it planned?

[daviftorres]

I do not know. I kinda suggested as I was replying to your discussion, because we run underclocked so it can accommodate all CPU speeds.