How to Limit WSL Memory Usage for Better Performance

Windows Subsystem for Linux (WSL) is a powerful tool that allows you to run Linux distributions directly on Windows without the overhead of a virtual machine. However, by default, WSL can use a significant amount of your system’s RAM, which may impact your overall system performance, especially if you have limited memory. Limiting WSL’s memory usage helps you control resource allocation, prevent slowdowns, and maintain a smoother Windows experience.

What You’ll Need

• A Windows 10 (version 1903 or later) or Windows 11 system with WSL installed.
• Basic familiarity with editing text files in Windows (Notepad or another text editor).
• Administrator access to modify system files if necessary.

Step-by-Step

1. Verify Your WSL Version: Open PowerShell or Command Prompt and run wsl --list --verbose. Note the WSL version (1 or 2) for your installed distributions, as memory management applies primarily to WSL 2.
2. Create or Edit the .wslconfig File: WSL 2 uses a `.wslconfig` file in your Windows user profile folder to configure global resource limits. Open Notepad or your preferred text editor and create a file named .wslconfig in C:\Users\YourUsername\ if it doesn’t already exist.
3. Define Memory Limits: Add the following section to the `.wslconfig` file:

   [wsl2]
   memory=4GB  # Limits VM memory to 4 GB
   processors=2  # Optional: limits WSL to 2 CPU cores

   Adjust the memory value to the amount you want to allocate. You can specify values in MB or GB (e.g., 2048MB or 2GB).

4. Save the File: Save the `.wslconfig` file and close the editor.
5. Restart WSL: To apply changes, restart the WSL service by running in PowerShell:

   wsl --shutdown

   Alternatively, you can reboot your PC.

6. Verify the Changes: Launch your WSL distribution again and check resource usage. You can run free -h inside WSL to see memory stats or monitor WSL’s VM memory usage in Task Manager under “WSL” or “Vmmem” processes.
7. Adjust as Needed: If you need tighter or looser limits, edit the `.wslconfig` file again, modify the memory value, save, and restart WSL.
8. Optional – Limit Swap Usage: You can also limit swap file size in the same `.wslconfig` file:

   swap=1GB  # Limits swap to 1 GB

   This helps control disk usage by WSL when memory pressure increases.

9. Optional – Use Distribution-Specific Configuration: For advanced users, you can configure resource limits on a per-distribution basis by modifying the `.wslconfig` or using Linux cgroups inside WSL 2, but this is more complex and less common.

Common Mistakes

• Editing the Wrong File Location: The `.wslconfig` file must be in your Windows user directory (e.g., C:\Users\YourUsername\), not inside the Linux filesystem.
• Incorrect Syntax: The `.wslconfig` file is sensitive to format. Make sure keys and values are correct and comments use #. Avoid extra spaces or unsupported units.
• Forgetting to Restart WSL: Changes won’t apply until you run wsl --shutdown or reboot your machine.
• Confusing WSL 1 and WSL 2: Memory limits apply only to WSL 2, as WSL 1 uses a different architecture without a VM.
• Setting Memory Too Low: Allocating too little RAM can cause applications inside WSL to crash or perform poorly. Balance your limits carefully.

Tips

• Monitor WSL Memory with Task Manager: The “Vmmem” process corresponds to WSL 2’s virtual machine. Watching its memory usage helps verify your limits.
• Use Powershell to Automate Configuration: You can script the creation or modification of `.wslconfig` to quickly apply changes across multiple machines.
• Combine Memory Limits with CPU Limits: Setting both memory and processors limits can help balance system load and ensure Windows remains responsive.
• Regularly Update WSL: Keep WSL and your Windows OS updated to benefit from improved resource management features.
• Backup Your .wslconfig File: If you rely on custom settings, back up your `.wslconfig` to avoid losing configurations during system changes.

Troubleshooting

If your memory limits don’t appear to be working or WSL is still using excessive memory, try the following steps:

• Confirm WSL Version: Run wsl --list --verbose to ensure your distributions are running under WSL 2, as the `.wslconfig` limits do not apply to WSL 1.
• Check .wslconfig Location and Syntax: Ensure the file is located at C:\Users\YourUsername\.wslconfig and contains correctly formatted keys and values.
• Restart WSL Properly: Run wsl --shutdown before restarting any WSL distribution to apply changes.
• Check for Conflicting Settings: Some third-party tools or scripts might override or conflict with `.wslconfig`. Disable or adjust them to isolate the issue.
• Inspect Swap Usage: If WSL is swapping heavily, consider lowering swap size or increasing memory limit to reduce disk I/O.
• Update Windows and WSL: Installing the latest Windows updates and WSL kernel updates can fix bugs affecting resource limits.
• Review Running Processes in WSL: Inside WSL, run top or htop to identify memory-hungry processes that might be causing high usage.

Frequently Asked Questions

Can I limit memory usage for WSL 1?

No, WSL 1 does not run inside a virtual machine and shares memory directly with Windows. Memory limits like those set in .wslconfig only apply to WSL 2.

What happens if I set the memory limit too low?

Setting memory too low can cause Linux applications to crash, slow down, or behave unpredictably due to insufficient resources.

Does limiting memory affect all WSL distributions?

Yes, the `.wslconfig` file applies globally to all WSL 2 distributions on your machine.

Can I set different memory limits per distribution?

Not directly via `.wslconfig`. Per-distribution resource limits require advanced configuration using Linux cgroups inside WSL, which is more complex and not officially supported.

How do I check the current memory usage by WSL?

Use Windows Task Manager to monitor the “Vmmem” process, which reflects WSL 2’s memory consumption. Inside WSL, use commands like free -h for Linux memory stats.

Will limiting memory improve Windows performance?

Yes, limiting WSL memory prevents it from consuming excessive RAM, leaving more resources for Windows and other applications, improving overall responsiveness.

Related

• Do You Have to Cook Green Beans? Facts and Food Safety Tips
• How to Prepare Fresh Green Beans: A Step-by-Step Guide
• When to Pick Green Beans: 10 Signs They’re Ready to Harvest