Seeing Hyper-V and Docker memory usage on Windows

This post explains how Hyper-V and Docker reserve memory on Windows machines that is outside of the normal process allocations.  It shows how you can see those reservations.

Docker and Hyper-V

Docker Desktop on Windows runs inside a Hyper-V virtual machine.  The virtual machine's memory is sized specified on the Memory setting in the Docker Control panel's Advanced tab.
Docker Desktop memory reservation.
That memory sizing maps directly to the Docker virtual machine's Assigned Memory value that is displayed in the Hyper V Manager Virtual Machines view. Hyper-V locks the virtual machine into memory by Drover Locking the VM's memory.  Memory used for VMs is partitioned away from the rest of the host's processes.
Hyper-V Manager VM's view
Hyper-V guest memory does not appear in TaskManager because it is reserved outside of the normal process structures.

Memory allocation by type with RamMap

Hyper-V virtual machine memory is allocated on the host and Driver Locked to keep it in memory and prevent usage by other Windows processes.  The SysInternals RamMap application displays Windows memory usage by usage type instead of by process.  This image shows that 16GB of memory has been Driver Locked.  This memory is allocated in the kernel outside of any regular Windows processes.
SysInternal RamMap

Weaknesses of the built in tools

Window's built in tools show overall memory usage and memory details by process. There can be huge differences between the two because memory may be allocated outside of the normal process boundaries.

Task Manager's Partial View

Task Manager shows that memory is being used. It does not show how it is used

Task Manager shows the total amount of memory in use via the Performance tab. It shows the memory that it is in use. It does not show how the memory is used.  
Memory in use on Performance tab
The Task Manager Processes view shows the amount of memory used by each process.  The Performance tab above showed 30GB in use.  The Processes tab does not show the virtual machine's memory reservation. The total memory shown consumed in the Processes tab is signficantly less that the amount shown in the Performance tab.
Task Manager Process tab

Resource Manager incomplete view

The bottom pane Windows Resource Manager shows a lot of memory in use.  The top pane again shows a total usage that when summed is missing the virtual machine.

Resource Manager memory usage

SysInternals

RamMap is just one of the components of SysInternals. Microsoft provides SysInternals tools free of charge.  






Comments

Post a Comment

Popular posts from this blog

Installing the RNDIS driver on Windows 11 to use USB Raspberry Pi as network attached

Image
I do a lot of my development and configuration via ssh into my Raspberry Pi Zero over the RNDIS connection. Some models of the Raspberry PIs can be configured with  gadget drivers  that let the Raspberry pi emulate different devices when plugged into computers via USB. My favorite gadget  is the network profile that makes a Raspberry Pi look like an RNDIS-attached network device.  All types of network services travel over an RNDIS device without knowing it is a USB hardware connection. A Raspberry Pi shows up as a Remote NDIS (RNDIS) device when you plug the Pi into a PC or Mac via a USB cable. The gadget  in the Windows Device Manager picture shows this RNDIS Gadget connectivity between a Windows machine and a Raspberry Pi. The Problem Windows 11 and Windows 10 no longer auto-installs the RNDIS driver that makes magic happen. Windows recognizes that the Raspberry Pi is some type of generic USB COM device. Manually running W indows Update  or  Upd...
Read more

Understanding your WSL2 RAM and swap - Changing the default 50%-25%

Image
The Windows Subsystem for Linux operates as a virtual machine that can dynamically grow the amount of RAM to a maximum set at startup time.  Microsoft sets a default maximum RAM available to 50% of the physical memory and a swap-space that is 1/4 of the maximum WSL RAM.  You can scale those numbers up or down to allocate more or less RAM to the Linux instance. The first drawing shows the default WSL memory and swap space sizing. The images below show a developer machine that is running a dev environment in WSL2 and Docker Desktop.  Docker Desktop has two of its own WSL modules that need to be accounted for.  You can see that the memory would actually be oversubscribed, 3 x 50% if every VM used its maximum memory.  The actual amount of memory used is significantly smaller allowing every piece to fit. Click to Enlarge The second drawing shows the memory allocation on my 64GB laptop. WSL Linux defaul...
Read more

Almost PaaS Document Parsing with Tika and AWS Elastic Beanstalk

Image
The Apache Tika project provides a  library capable of parsing and extracting data and meta data from over 1000 file types.  Tika is available as a single jar file that can be included inside applications or as a deployable jar file that runs Tika as a standalone service. This blog describes deploying the Tika jar as an auto-scale service in Amazon AWS Elastic Beanstalk.  I selected Elastic Beanstalk because it supports jar based deployments without any real Infrastructure configuration. Elastic Beanstalk auto-scale should take care of scaling up and down for for the number of requests you get. Tika parses documents and extracts their text completely in memory. Tika was deployed for this blog using EC2 t2.micro instances available in the AWS free tier. t2.micro VMs are 1GB which means that you are restricted in document complexity and size. You would size your instances appropriately for your largest documents.   Preconditions An AWS account. AWS ac...
Read more