Taming the Memory Hog: How to Control Vmmem in WSL

It's a familiar frustration for many of us who rely on the Windows Subsystem for Linux (WSL) for our development or other tasks: you're deep in a download, compiling code, or running a complex process, and suddenly, your system grinds to a halt. A quick peek at Task Manager reveals the culprit – the vmmem process is gobbling up an alarming amount of RAM, and it just keeps climbing.

This isn't just an annoyance; it can seriously impact your system's performance, making everything else sluggish. You might wonder if there's a way to rein in this memory-hungry process without having to shut down your entire WSL environment, especially when you're in the middle of something important. Thankfully, the answer is a resounding yes.

The key lies in a simple configuration file that acts as a control panel for your WSL 2 instance. By creating or modifying a file named .wslconfig in your user profile directory, you can set explicit limits on how much memory vmmem is allowed to consume.

Here's how you can get this done:

First, you'll need to navigate to your user profile folder. The quickest way is to press Windows + R, type %userprofile%, and hit Enter. This will open your user directory in File Explorer.

Once you're there, look for a file named .wslconfig. If it doesn't exist, don't worry – you can simply create a new text file and name it .wslconfig. If it's already there, you'll just be editing the existing one.

Now, open this .wslconfig file with your preferred text editor (like Notepad, VS Code, or any other). You'll want to add the following lines:

[wsl2]
memory=2GB
swap=0
processors=2

Let's break down what these lines do:

• [wsl2]: This simply indicates that the following settings apply to WSL 2.
• memory=2GB: This is the crucial line. It sets the maximum amount of RAM that WSL 2 (and thus the vmmem process) can use. I've set it to 2GB here as an example, but you should adjust this value based on your system's total RAM and your typical workload. If you have 16GB of RAM, you might comfortably set this to 8GB or even 10GB, leaving enough for Windows itself.
• swap=0: This disables the swap file for WSL. While swap can be useful, it can also lead to performance issues if WSL starts heavily relying on it. Disabling it can sometimes help keep memory usage more predictable.
• processors=2: This allows you to specify how many virtual processors WSL can use. Again, adjust this based on your CPU. If you have an 8-core processor, you might set this to 4 or 6, depending on your needs.

After you've saved your .wslconfig file, the changes won't take effect immediately. You need to restart WSL. The most reliable way to do this is to open PowerShell or Command Prompt (as administrator is often recommended for this) and run the command:

wsl --shutdown

Once WSL has shut down, the next time you launch a Linux distribution, it will start with the new memory limits you've set. You should notice that the vmmem process no longer grows unchecked and stays within the boundaries you've defined.

It's worth noting that while this configuration helps manage memory, it doesn't inherently grant WSL access to your GPU. For tasks that require GPU acceleration, like AI development, there are separate configurations and driver setups needed, which is a whole other fascinating topic!