1 Reply Latest reply on Jul 10, 2018 2:16 AM by sxnxr

    VM Rightsizing Differences between 6.3 & 6.7

    cgrvy Enthusiast

      Are there differences in the way vROPS does rightsizing between version 6.3 and 6.7 that anyone is aware of?

       

      I have a report for my environment that shows a VM recommendation of changing from having 32GB to 30GB using vROPS 6.3, however when running the report in vROPS 6.7 that recommendation has changed to 16GB.

       

      Thanks.

        • 1. Re: VM Rightsizing Differences between 6.3 & 6.7
          sxnxr Expert

          6.7 changed the counter that was used for CPU and Memory right sizing.

           

          in versions prior to 6.7 i think it used the Active memory counter which is the active memory used on the ESXi host not what the guest was using so traditionally you could reclaim more memory and everyone's dashboards were green

           

          Now 6.7 drops and it uses the guest free memory counter. This looks at the free memory in the guest as it is the safest memory to remove. This is one the 3 major counters for capacity & performance monitoring. The other 2 counters are Page-in Rate and Commit Ratio. In Windows, this excludes the cached memory. If this number drops to a low number, Windows is running out of Free RAM.

           

          If windows runs out of free ram it will start to page which is where the Paged-in Rate metric comes into play. In windows if you click on the open resource monitor in task manager and select the memory tab you can see the standby memory and the free ( Application cache is the creater of standby memory). the Guest|Needed memory counter in vrops is the windows active + the standby/cache memory)

           

          This change has been controversial at best but personally i like it as it gives me a better view of my memory landscape. It did however cause me to adjust some of the dashboards to turn them back to green as 90% of the VMs started showing a higher memory utilisation because it now took the application cache into account.

           

          In your case i would have expected to see it the other way around (6.3 reclaiming more and 6.7 less) but just be aware you are not comparing the same metric