CDV33
Contributor
Contributor

RAM Sobredimencionada

Jump to solution

Estimados, buenas tardes, por favor sus conocimientos para entender lo siguiente:

Tengo una MV (Windows Server 2008 R2), Memoria RAM asignada: 32 GB.

Al supervisar la MV en Tiempo Real por vSphere Client (6.5), me informa un máximo de 5.0 GB y al mismo tiempo el administrador de tareas de Windows me informa 10.6 GB en uso.

Esto quiere decir que la maquina esta sobredimencionada en RAM?

Como saber la cantidad real de RAM que debo asignar a la maquina virtual?

Agradecería demasiado sus comentarios.

Saludos,

Claudio

0 Kudos
1 Solution

Accepted Solutions
ThompsG
Virtuoso
Virtuoso

Hi there CDV33,

The 5Gb you see in the vSphere client is likely the “active” memory, which is pages on the ESXi host which have recently changed. Now please note this is not unique blocks so cannot be used accurately for sizing memory as it could be very wrong.

To to use your example, it could be that when you look back over the last hour the VM only has 5Gb of active memory during that whole time. This might lead you to think the VM is only using 5Gb however inside the guest it might be changing/modifying/using a different 5Gb of memory every sampling period.

The true measure is to look inside the VM and use those counters.

For Windows guests the ones I like to use from Task Manager are:

  • Committed (Gb)
  • Free

The Committed is made up of physical memory and paging file so can be a good indicator of exactly what the guest is using. Add to this check the Free memory as these are pages which are free and immediately available for use. If there is constantly free memory available, then you could likely reduce the memory allocated to the VM as this a high Free memory counter would be indicating that the guest has more memory than it needs.

Does this make sense? If further help required then please post a screenshot of your Task Manager.

View solution in original post

0 Kudos
2 Replies
ThompsG
Virtuoso
Virtuoso

Hi there CDV33,

The 5Gb you see in the vSphere client is likely the “active” memory, which is pages on the ESXi host which have recently changed. Now please note this is not unique blocks so cannot be used accurately for sizing memory as it could be very wrong.

To to use your example, it could be that when you look back over the last hour the VM only has 5Gb of active memory during that whole time. This might lead you to think the VM is only using 5Gb however inside the guest it might be changing/modifying/using a different 5Gb of memory every sampling period.

The true measure is to look inside the VM and use those counters.

For Windows guests the ones I like to use from Task Manager are:

  • Committed (Gb)
  • Free

The Committed is made up of physical memory and paging file so can be a good indicator of exactly what the guest is using. Add to this check the Free memory as these are pages which are free and immediately available for use. If there is constantly free memory available, then you could likely reduce the memory allocated to the VM as this a high Free memory counter would be indicating that the guest has more memory than it needs.

Does this make sense? If further help required then please post a screenshot of your Task Manager.

0 Kudos
CDV33
Contributor
Contributor

Hola ThompsG,

Muy agradecido por tu respuesta y solicito nuevamente tu ayuda para entender los valores relacionados a la Memoria:

pastedImage_0.png

Saludos,

Claudio

0 Kudos