locked
Difference in Perfomance Counters RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Members,

    We have Linux VM on which we assigned dynamic memory approx 20 GB and 8 Logical Processor.

    Machine was performing slow for which i just just checked inside VM performance its memory utilization shows 19 GB and processor usage shows 98 % while on hyper-v manager it shows 17 GB utilization of memory and only 35 % processor utilization.

    can someone explain which one shows correct figures

    Inside VM or hyper-v manager ?

    Tuesday, April 7, 2015 8:00 AM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    Both are correct. 

    For the efficient running of a VM try to keep CPU utilization down below 80%, I find the about 65-70% is a good number.

    The Hyper-V Manager is showing the utilization on the host not the VM. 

    Here's a more thorough explanation:

    http://blogs.technet.com/b/haroldwong/archive/2013/03/08/hyper-v-2012-dynamic-memory-what-does-the-vm-think-it-has-versus-what-it-really-has.aspx

    Cheers

    Andrew

    Cheers! Andrew

    • Proposed as answer by BrianEhMVP Tuesday, April 7, 2015 2:56 PM
    • Marked as answer by Elton_Ji Monday, May 11, 2015 5:43 AM
    Tuesday, April 7, 2015 12:40 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Sir,

    You can use performance monitor in hyper-v host with the counter "Hyper-v Dynamic Memory VM" , there will be two properties "Guest Visible Physical Memory" and "Physical Memory" .

    "Guest Visible Physical Memory " in your case is 19GB .

    "Physical Memory " in your case is 17GB showing in hyper-v manager , it is the physical memory the VM is using .

    Regarding CPU usage , the CPU usage  in hyper-v manager will show the physical hyper-v host's CPU usage , if you allocate same number as host's LP number to VM then the VM's CPU usage will be close to Host's CPU usage .

    Best Regards,

    Elton Ji

    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com .

    • Proposed as answer by Elton_Ji Wednesday, April 29, 2015 6:21 AM
    • Marked as answer by Elton_Ji Monday, May 11, 2015 5:43 AM
    Wednesday, April 8, 2015 4:58 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    Both are correct. 

    For the efficient running of a VM try to keep CPU utilization down below 80%, I find the about 65-70% is a good number.

    The Hyper-V Manager is showing the utilization on the host not the VM. 

    Here's a more thorough explanation:

    http://blogs.technet.com/b/haroldwong/archive/2013/03/08/hyper-v-2012-dynamic-memory-what-does-the-vm-think-it-has-versus-what-it-really-has.aspx

    Cheers

    Andrew

    Cheers! Andrew

    • Proposed as answer by BrianEhMVP Tuesday, April 7, 2015 2:56 PM
    • Marked as answer by Elton_Ji Monday, May 11, 2015 5:43 AM
    Tuesday, April 7, 2015 12:40 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Sir,

    You can use performance monitor in hyper-v host with the counter "Hyper-v Dynamic Memory VM" , there will be two properties "Guest Visible Physical Memory" and "Physical Memory" .

    "Guest Visible Physical Memory " in your case is 19GB .

    "Physical Memory " in your case is 17GB showing in hyper-v manager , it is the physical memory the VM is using .

    Regarding CPU usage , the CPU usage  in hyper-v manager will show the physical hyper-v host's CPU usage , if you allocate same number as host's LP number to VM then the VM's CPU usage will be close to Host's CPU usage .

    Best Regards,

    Elton Ji

    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com .

    • Proposed as answer by Elton_Ji Wednesday, April 29, 2015 6:21 AM
    • Marked as answer by Elton_Ji Monday, May 11, 2015 5:43 AM
    Wednesday, April 8, 2015 4:58 AM