Urgent.News

What's breaking now, across hundreds of outlets.

Tech

I tested 16GB, 32GB, and 64GB of RAM in the same gaming PC, and found out when more memory actually matters

More RAM doesn't help unless you're running out of it.

I tested 16GB, 32GB, and 64GB of RAM in the same gaming PC, and found out when more memory actually matters

The debate over how much RAM is needed for gaming PCs remains unresolved, especially in the current market with high component prices. Many people suggest 16GB, 32GB, or even 64GB. I conducted an experiment using a gaming PC with a Ryzen 7 9800X3D and RTX 5070, testing 16GB, 32GB, and 64GB of DDR5-6000 RAM in four games at 1080p.

Across all four games, game frame rates and memory usage remained virtually unchanged between 16GB and 32GB. While 16GB struggled during peak gameplay with minimal background applications, 32GB provided a much smoother experience, allowing for smoother gameplay with up to 10GB of spare memory. Doubling to 64GB didn't improve performance, as the games tested did not approach 32GB capacity.

For most gaming scenarios, 32GB is more than adequate. However, for non-gaming or power-user tasks like running multiple virtual machines, containers, or large language models, 64GB offers additional headroom. Currently, 16GB is sufficient for gaming and web browsing, making it a cost-effective choice. Upgrading to 32GB when prices decrease is recommended, as 16GB was nearing its limit even in less intensive scenarios.

Rewritten by urgent.news; may contain errors — check the original.

Read the original at xda-developers.com →

Report a problem with this story

More in Tech

Deleted Documents Still Answer

Originally published at Trida AI . You delete the file. The assistant keeps quoting it. That is not a model failure, and it is not a retrieval failure either.

  • RAG systems maintain two document copies: source and index.
  • Deletion detection is not automatic in RAG systems.
  • Soft-delete strategy required to handle deletions.

What Checking Every Scheduled Run, Not Just the Latest, Actually Caught

42 scheduled runs so far, 5 of them failed outright, and not one of those 5 ever surfaced on its own. No email, no notification, no red mark anywhere I'd naturally look.

  • 42 scheduled runs conducted, but 5 failed without alert
  • Failures went undetected until routine manual checks
  • Status check with Get-ScheduledTaskInfo caught issues

More from Saturday 21 November →