Performance

This page is related to getting maximum performance for the container.

Windows

Hardware

Use >16GB of RAM

I haven't tested the exact amount of RAM that's the actual minimum, you may get away with 8GB as well, but during my testing 16GB was definitely the most stable. It was primarily VSCode that had a nasty habit of crashing if you went over budget, technically WSL and Docker were just slowed down.

Software

Use WSL

Disk I/O is terrible unless you first move your project into the WSL filesystem. So not just opening the folder in WSL, but actually moving it to e.g. ~/projects/my-app.

Alternative to WSL, clone into a volume

If you clone your repository into a volume using >Dev Containers: Clone Repository into Container Volume you can avoid having to install WSL. In my experience, WSL is more performant and easier to use, not to mention that in order for your volume to persist between builds you'll need to use a named volume instead. It's an option, but not one that I'm looking too deep into because I so strongly support using WSL instead.

Mac

Hardware

Use >16GB of RAM

I haven't tested the exact amount of RAM that's the actual minimum, you may get away with 8GB as well, but during my testing 16GB was definitely the most stable. It was primarily VSCode that had a nasty habit of crashing if you went over budget, technically WSL and Docker were just slowed down.

Linux

Hardware

Use >16GB of RAM

I haven't tested the exact amount of RAM that's the actual minimum, you may get away with 8GB as well, but during my testing 16GB was definitely the most stable. It was primarily VSCode that had a nasty habit of crashing if you went over budget, technically WSL and Docker were just slowed down.