RAM Disk on Windows 11

How hard is for some people to understand that you can have up to 128GB on a workstation nowadays and want chunk of 100GB to be loaded inside the ram, for several reasons, like compilation or in my case, data that is loaded because I have to do a repeated task connecting and disconnecting from accounts that need loading several GBs every time and while doing that thousands of small files are written or read, most o them around 100KB to 20MB.

M.2 are good? yes they are, but doing tasks like this burn M.2 literally by overheating(not just the usage) random read/writes are most costy to storage devices, i needed a cooler on top of mine, cause it was touching 90ºC easily, then i got a secondary one, to split from main system.

Buying the second m.2 cost me about the same price as buying more 2x 32GB sticks of ram would btw, with 10% of the actual benefit it would.

There are dozens of situations that using RAM storage, either as a temp/cache or as copy, that is not going to be saved after, would be essential.

But the main point is, speed is a major factor, cause 10x the speed is a lot and that factor is highly unlikely to ever change.

Yes, there are 3rd party software around, but they often end up with dozens of issues that are affected by system updates breaking them, or apps resetting/deleting mklink junctions for instance, i used to have imdisk in windows 10, but got tired of redoing the junctions and having to restore backups.

This happens because even though symlinks are a system thing, they are not default behavior, so apps won't support and the system most of the time won't pass the path like if they were real path, which microsoft could do with a snap a finger.

BTW ramdisk is not really that different from caching, which already exists, but the current format denies us real access to control the limit of the cached data and it could easily allow us to pre cache entire folders, in fact this behavior already exists to some level in file servers.

I'm really hoping that the new keys found in a recent update are somehow a way to increase caching waay beyond current levels.

NtfsCachedRunsBinMaxLengthInBytes"=hex(b):00,00,00,00,00,00,00,00
"NtfsCachedRunsDelta"=hex(b):00,00,00,00,00,00,00,00
"NtfsCachedRunsInsertLimit"=hex(b):00,00,00,00,00,00,00,00
"NtfsCachedRunsLimitMode"=hex(b):00,00,00,00,00,00,00,00

Otherwise i might just end up going back to W10 or W7.

German language

Was soll eigentlich inner die Behauptung, nimmt Speicher weg. Fahre auf meinem alten DualCore-Lappy Win7 32Bit und habe da 1 RamDisk von 700MB im nicht benutzen Speicherbereich unterhalb 3GB zum Swappen und Temp. Dort komme ich auf Traumwerte bis 3GB/s und oberhalb von 3GB noch eine 5GB RamDisk mit bis zu 2GB/s. Und wenn ich meinen grossen Rechner anwerfe, 2x Xeon je 10C/20T mit 16x16GB=256Gb, da fahre ich meine ganzen BTSen im Ram mit RamDisk, zumeist unter Linux. Und ich benutze schon seit 45 Jahre für Messlogging und Simulationen jeweils die Ramdisk. Es liegt also wohl an dem jeweiligen Betrachter, warum Er gerne eine RamDisk für Win11 nutzen möchte. Mfg BB

Translated to English language

What is actually supposed to be inside the claim, takes away memory. I drive on my old DualCore-Lappy Win7 32Bit and have 1 RamDisk of 700MB in the unused memory area below 3GB for swapping and temp. There I get dream values up to 3GB/s and above 3GB a 5GB RamDisk with up to 2GB/s. And when I start my big computer, 2x Xeon each 10C/20T with 16x16GB=256Gb, I run all my BTSes in Ram with RamDisk, mostly under Linux. And I've been using it for 45 years.

Moderator note < Translated to English language >

I agree.

In my case I would use ffmpeg to compress video and store it in chunks for HLS stream transmission. If I create a continuous feed that is going 24/7 for days on end, the chunks will be written and overwritten so many times on my SSD that it will wear it out prematurely. Instead, on a Linux or MacOS system I would create and write to a RamDisk so as not to wear out the non-volatile storage of a disk drive. It also wouldn't chew up bandwidth on the interface for said storage drive.

So this is another legitimate use case and why Linux, BSD, MacOS, and others still provide the facility to have a RamDisk. It sounds like Microsoft is not providing this. ? If this is true then it is simply "sad".

I totally agree and that is proven by the impact of the data rates to/from disk having high impact on overall compilation time.

I agree, but you may use third party RAM disk software and this software is selling officially, isn't it?

Hello,

Thanks for all the information provided.
Please refrain from judging whether a ramdisk is a solution or not for one user or another: You simply cannot know and the question was not about what you think about a ramdisk, but how do make one...

As pointed out above, compilation is one of the possible use cases, which can profit from the use of a ramdisk, I totally agree and that is proven by the impact of the data rates to/from disk having high impact on overall compilation time.

I'd highly appreciate an official and stable solution for professional application.

Regards

PS: In a professional environment, for instance the investment for just 32GB supplementary RAM can financially be justified if it speeds up work a little and thus reduces delay / work hours.