April 27, 2026
When upgrades go full downgrade
Mo RAM, Mo Problems
More RAM, less speed? Retro nerds sound off
TLDR: A 1998-era PC ran Quake slower after adding RAM because the motherboard couldn’t speed-boost (cache) memory past ~128MB, so Windows loaded into the slow zone. Commenters split between ‘it’s a chipset limit,’ ‘try tag RAM or Linux swap hacks,’ and ‘even Chrome hoards memory today’.
Retro PC land is in meltdown after one builder made his 1998 Quake rig faster by removing RAM. He loaded up bargain-bin memory and watched frame rates plunge 25%. Why? Old motherboards could only “speed-boost” a small chunk of memory with L2 cache (a tiny fast buffer); add too much RAM (the computer’s short‑term memory), and Windows shoved itself into the slow lane. Cue the drama.
Some commenters swear it’s a classic 90s gotcha. “Extensible tag‑RAM,” insisted MrBuddyCasino, stirring a mini‑mystery over whether the fix is a hardware add‑on or just false advertising on the board’s spec sheet. Others turned the flamethrower on today’s software: “Chrome, I’m looking at you,” snapped one user, claiming modern apps still bloat themselves just because they see more memory.
Then came the hacks. Cockbrand flexed an old Linux trick: treat everything above 64MB as a RAM disk for swap so the fast bit stays fast, a move the thread hailed as peak penguin wizardry. Nostalgia poured in too: tales of dual‑CPU machines dropping cache, and 2000s laptops booting slower with more memory sparked a chorus of “more ain’t always more.” The meme of the day: “Remove a stick, gain an FPS tick.”
Key Points
- •A 1997-era Quake PC initially achieved 44.6 fps on a Pentium MMX 233 MHz but later dropped to 33 fps after changes.
- •Extensive troubleshooting showed that having two or more RAM modules installed caused the slowdown; a single module restored performance.
- •The 430FX chipset caches only the first 64 MiB of RAM; Windows 95/NT allocate from the top down, placing OS/apps in non-cached memory when RAM exceeds cacheable limits.
- •The XA100 motherboard, advertised to cache 512 MiB, effectively cached about 128 MiB in practice, leading to performance loss beyond that.
- •Reducing installed RAM brought performance back, illustrating that too much memory can hurt speed on certain older chipsets.