296
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 28 Aug 2026
296 points (99.3% liked)
PC Gaming
15364 readers
950 users here now
For PC gaming news and discussion. PCGamingWiki
Rules:
- Be Respectful.
- No Spam or Porn.
- No Advertising.
- No Memes.
- No Tech Support.
- No questions about buying/building computers.
- No game suggestions, friend requests, surveys, or begging.
- No Let's Plays, streams, highlight reels/montages, random videos or shorts.
- No off-topic posts/comments, within reason.
- Use the original source, no clickbait titles, no duplicates. (Submissions should be from the original source if possible, unless from paywalled or non-english sources. If the title is clickbait or lacks context you may lightly edit the title.)
founded 3 years ago
MODERATORS
I thought 32GiB would be enough coming from 16, but nope, I found a new use case where it's too little.
Originally, I wanted to be able to run at least 2 VMs with 8GiB assigned at once.
But the new use case is a 4GiB RAM VM with 20GiB virtual disk stored in RAM (TMPFS). And that's not all that much.
I've also just been using it for random temporary things, as I am still paranoid about SSD wear. If I need to download an ISO just to burn it, there's no need to take, say, 3GiB from the SSD's lifespan, no matter how small that may seem.
But even if not used explicitly, it's still pretty useful for disk I/O cache. Especially with slow things like memory cards. At least for reading, for writing it's just annoying because I have no idea how much has already transferred, and neither can I safely stop it.