I suggest you ...

DCR: Customer would like a better algorithm for calculating Overcommit

Customer is sometimes 'ok' state. And other times, 'overcommit' state, even without changes in environment.

SCVMM 2016 UR4, Standalone VMM environment of 12 Nodes.
He has 192 GB free when he calculates all his HOST's free memory including the reserve node's (R1).

https://support.microsoft.com/en-us/help/3023928/details-of-the-cluster-overcommit-algorithm-in-system-center-2012-r2-v

* What we might really need here is logging of how 'ok' and 'overcommit' was calculated so the toggle between both states is understood.

5 votes
Vote
Sign in
Check!
(thinking…)
Reset
or sign in with
  • facebook
  • google
    Password icon
    Signed in as (Sign out)
    You have left! (?) (thinking…)
    KAREL DEVLUGT shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →

    1 comment

    Sign in
    Check!
    (thinking…)
    Reset
    or sign in with
    • facebook
    • google
      Password icon
      Signed in as (Sign out)
      Submitting...
      • Anonymous commented  ·   ·  Flag as inappropriate

        I would suggest changing the title of this post to "Better visibility of the Overcommit calculations and/or reason. As you say, that is what we really want/need.

      Feedback and Knowledge Base