I'm starting a full-time software development role and currently use my own Windows PC during probation. My workload includes TypeScript/Node, React, Python, Docker, databases, and some local AI tooling. My Docker environment already uses about 5 GB of RAM for services such as PostgreSQL, Redis, and Keycloak, while VS Code, Firefox, Discord, Claude, and other development processes bring my 16 GB system close to its limit. Firefox alone can sometimes use nearly 4 GB.
My PC has a Ryzen 5 5600, an RX 9060 XT with 16 GB VRAM, an ASRock B450M Steel Legend motherboard, and 16 GB of DDR4-3200 CL16 in a 2x8 GB kit. The system drive is a nearly full 256 GB NVMe SSD, with code and other files on a 2 TB hard drive.
I'm considering either adding another 2x8 GB kit for 32 GB total, replacing the current memory with a 2x16 GB kit while keeping the old kit as a spare, or spending considerably more on 2x32 GB for 64 GB. I may eventually add a larger SSD, but I'd prefer not to upgrade everything at once.
For this kind of Docker-heavy development, is 32 GB enough, or would 64 GB provide a worthwhile benefit? Also, are there any Ryzen 5000, AM4, or B450 compatibility and stability concerns when replacing the current 2x8 GB kit?
3 Answers
For a Windows development setup with Docker, databases, an IDE, browsers, and several background tools, 16 GB is definitely the limiting factor. In a similar .NET/React/SQL workflow, 16 GB was constantly cramped, 32 GB was comfortable, and 64 GB provided useful extra headroom. I’d choose a matched 2x16 GB DDR4-3200 kit rather than mixing another 2x8 GB kit. That gives you 32 GB now and leaves the old kit available as a backup.
Before buying 64 GB, check when your employer’s computer is actually scheduled to arrive. If you need an upgrade immediately, 32 GB is a reasonable stopgap. For the motherboard, use a matched kit rated for DDR4-3200, update the BIOS if needed, and enable XMP/DOCP after installation. Four DIMMs can be more demanding on the memory controller and may require a lower speed or manual stability adjustments, so 2x16 GB is generally the safer choice on AM4.
I’ll check the work-computer timeline and look for a properly matched 2x16 GB kit rather than filling all four slots. That also avoids losing my current kit as emergency RAM.
WSL and Docker can reserve a substantial amount of memory separately from normal Windows applications, so 16 GB becomes uncomfortable surprisingly quickly even with a moderate stack. Thirty-two gigabytes should be sufficient for most development workloads, while 64 GB is worthwhile if you run many containers, multiple databases, local virtual machines, large builds, or heavier local AI tools at the same time. Unless you already see memory usage or swapping approaching 32 GB, 64 GB is probably unnecessary for now.
That sounds like the sensible compromise. I mainly want enough room for the full local environment without spending heavily on 64 GB before I know whether I’ll actually need it.