During a call it was discussed that VMware rightsizing provided usually wrong results on Memory.

Why is this the case:

It appears there's a known issue where VMware Rightsizing provides inaccurate data, and the customer was aware of this.

The core of the problem likely stems from shared memory (SHM) within the VM, as the kernel often reports SHM as cache, leading to miscalculations in rightsizing recommendations.

GOALS of this Spike:

Learning
Maybe update Documentation
Maybe update CNV Rightsizing

This should not block current TP/GA progress on this feature