RAM Disk on Windows 11

There are very good reasons to have a RAM disk now with SSD drives. RAM is great, it doesn't really wear, it's only "flaw" is that it loses data when power is lost. SSD drives have finite maximum writes.

Of course, there's all kinds of optimization so theoretically it should take the "typical" user a very long time to reach the write limits. But if you're working with a lot of data or there's constant writing going on that's not good for an SSD.

I've read 300 to 1000 write cycle limitations per cell or triple cell. For that matter, why not forget trapping electrons or UV erasable ROM and go back to permanent write-once ROM that burns tiny fuses and just makes it 300 times the target capacity? If it could be done fast enough that would be great and a bonus is that data will never be lost and have the same "write" limitations.

I feel uneasy thinking about paging files now. Many programs constantly write to the hard drive. I was shocked to find out how much Chrome was constantly writing due to their use of MySQL database. With modern databases like Snowflake, if you're not able to write directly to cloud data storage, Snowflake expects bulk data uploads to be done with a local file.

If I'm doing automation gathering a lot of data regularly to push into a snowflake database, I have to first write it to disk and then the Snowflake driver can upload it to its staging area to be copied into a table. No practical way to do it all in memory so that's a lot of wasteful temporary writes to the SSD.

I automate a lot of processes to gather data and I've often had needs to create temporary files on the local drive. You can't always practically do everything in memory because utilities and tools have typically been designed to read and write to files. Researching and sharing data between applications often has suggestions to write to files.

While pipes could have been a nice option they open up a can of worms with security tools and IT departments and any software I create to use named pipes often gets flagged as suspicious. The most simple solution to this is a RAM disk. Fast reading and writing temporary files with no worries of disk wear would be awesome. A RAM disk would be really great to have for automation.

It would be even better if it was just included in Windows so I wouldn't need to use a 3rd party tool that I have to explain to an IT security department. It's solved my problem with Chrome. Chrome had the most constant disk writes of any application, while it was idle. I'd leave my computer running for months with Chrome open and I can't imagine the extent of what has been written.

Using a RAM disk I took a minimal configuration for Chrome with all my passwords, cookies, and bookmarks, zipped it up and I just extracted that to the RAM disk and set up a Chrome shortcut to use the ChromeData folder there. No more SSD disk writes from Chrome. I'd really like an integrated Microsoft RAM disk feature.

Maybe there's a way to have an option to periodically write its image to a real fixed-length storage file, only updating bytes that have changed and doing it far less frequently than what's going on now with programs using temporary files. Or even better, have it cloud drive synced so it's really not my problem.

Answers like yours saying "There is no use".

Sorry but seems this is some misunderstanding. I did not say these words.

If I have 128GB, I specifically may want to 64GB for Visual Studio files.

Answers like yours saying "There is no use" is a disservice to those who like to tweak and optimize their machines.

Still, even with a 16GB build, if the user's daily workflow maxes out at a significantly smaller amount, the benefits of a reliable/stable RAM disk would still be of benefit.

Sorry, but can you provide any (reliable) test results as confirmation?