Setting Up WSL 2 (Windows Subsystem for Linux) for High-Performance Coding

Why WSL 2 is a Game Changer for Windows Developers

Historically, developers using Windows had to choose between dual-booting Ubuntu, running heavy VirtualBox VMs, or dealing with subtle cross-platform incompatibilities. WSL 2 provides a real, lightweight Linux kernel running inside a Hyper-V architecture, giving you full access to Linux CLI tools while keeping Windows as your daily desktop operating system.

1. Installing WSL 2 on Windows 10 & 11

Open Windows PowerShell as Administrator and run:

wsl --install -d Ubuntu-24.04

Reboot your machine when prompted, then set your default Unix username and password.

2. Restricting WSL 2 RAM Consumption with .wslconfig

By default, WSL 2 can allocate up to 50% to 80% of host RAM for its page cache, potentially leaving Windows applications starved of memory. Create a global configuration file at C:\Users\<YourUsername>\.wslconfig:

[wsl2]
# Limit Linux VM memory to 6GB
memory=6GB

# Allocate 4 CPU cores
processors=4

# Set swap storage
swap=4GB

# Enable localhost networking forwarding
localhostForwarding=true

Restart the WSL subsystem in PowerShell via wsl --shutdown.

3. CRITICAL: Avoid the Cross-Filesystem Performance Trap

One of the most common mistakes is storing source code inside the Windows NTFS partition (e.g. /mnt/c/Users/Mohit/projects) and running Linux compilers over it. Cross-filesystem translations cause a 5x to 10x I/O slowdown.

• Slow: /mnt/c/projects/my-app (NTFS filesystem crossing)
• Fast: /home/mohit/projects/my-app (Native ext4 Linux filesystem)

4. Integrating VS Code with WSL

Install the WSL extension in VS Code. From your Ubuntu terminal, navigate to your project directory and type:

code .

VS Code boots seamlessly with the editor interface running in Windows while language servers, terminal instances, and compilers execute natively inside Ubuntu.