What is the best way to load Windows and the entire system partition directly into a RAM disk when starting the computer?

Question

Microsoft

For a long time, since 2011, I want to stir up such a scheme as an experiment to eliminate bottlenecks in the I / O of a home workstation.
Given

• Windows 10 Pro + working software + resident software;
  
• 64 GB of fast memory, of which approximately 44-48 GB is dedicated to the RAM disk;
  
• 44-48 GB system partition on SSD.
  

Plan
When the computer starts, the system partition is fully loaded into the RAM disk. Every night the difference is synchronized with the contents on the physical disk (and again forcibly when the UPS is activated). Subsequently, the same approach can, for example, be applied to a laptop and, among other things, win in power consumption due to media downtime (yes, homeopathy - but nice).
Implementation is scheduled for the end of the year (I'm waiting for new motherboards), but I would like to try to thoroughly investigate this issue in advance.
Meaning
Reading and writing to the disk occurs at the speed of accessing RAM, that is, even without microscopic delays (because the information goes past the SATA / PCIe bus; theoretically, all exchange should occur only between the memory and the processor). No need to worry about wear, amplification and other nonsense. Plus, if something irreparable happened to the system , in most cases it will be possible to roll back with a normal reboot, but this is a small bonus.
Thus, the problem of lack of I / O for the most demanding work applications and the system will be solved once and for all, and the processor (or, there, the video card) will already be bottled. Plus, the vast majority of everyday activities will occur with the greatest possible responsiveness. The solution is interesting from both theoretical and practical points of view.
Problem

• How / with what can you create a bootloader that will create a virtual partition, copy the contents of the SSD into it and load Windu from there? The stumbling block seems to be the creation of a virtual partition outside the booted system. So far, only Linux + a virtual machine comes to mind, but working through a padding system seems like a dubious solution. (If I used only Linux, it would be much easier, I understand.) A few years ago, a friend did a similar experiment here with Win7 using GRUB4DOS, but, as far as I understood, in his case, the image lay ready on the physical disk before booting, which, of course, is feasible, but not so practical (of course, if I correctly understood what exactly he did).
  
• How / what is the best way to synchronize the difference so as not to create unnecessary load on the physical disk? Theoretically, you can get by with NTFS links; synchronization will be faster, but then there will be many extra entries, and this is not entirely desirable.
  

What answers do not expect

• You don't need it - you need it, you really need it. :)
  
• Inefficient - most of the disk will be occupied by static files - I do not argue. However, in this case, I'm not pursuing efficiency. I would like to at least test the technology on real tasks. Excess memory in extreme cases can be sold.
  
• You won't have enough space - oddly enough, enough .
  
• Buy Optane or a top-end PCIe-SSD - it's more convenient, but even more expensive than extra memory, and still not faster. And load the tire.
  

Answer 1

Through the hypervisor, you can check if the difference in performance. Place the same system image on ssd and ramdisk and run tests.
Or here - forum.ru-board.com/topic.cgi?forum=62&topic=24404 It's true about 7, but maybe 10 will start like that.

Answer 2

What is the best way to boot Windows directly into a RAM disk when starting the computer?

Believe it or not, you don't have to do anything for it. In any case, it is loaded into RAM at system startup, by itself.

an experiment to eliminate bottlenecks in the I/O of a home workstation.

Any modern SSD is guaranteed to eliminate all I/O bottlenecks if you put your system on it. A further increase in disk IOPS will have no effect, for the simple reason that there will no longer be a bottleneck. This is a fact that has been repeatedly tested and proven.

No need to worry about wear, amplification and other nonsense.

Well, worrying about SSD and HDD wear is pretty silly in this case. But what is recording amplification is not entirely clear.

Thus the problem of lack of I / O for the most demanding work applications

This will in no way solve the problem of lack of I / O for demanding applications, for this it is necessary to load into RAM not the system, and not even the application, but the data with which applications work, and the folder in which these applications store their caches, and other intermediate results.

You won't have enough room - oddly enough, enough.

Are you seriously 16GB takes a dozen?
And does this size include the swap file? Or did you turn it off???

64 GB of fast memory, of which approximately 44-48 GB is dedicated to the RAM disk;

Believe the best in this situation is to give this memory to the system, and not sculpt RAM drives, so it will be used most optimally and bring more benefits.
The exception is old, crooked applications that do not know how to efficiently use memory and exploit the disk insolently. Sometimes it makes sense to load them into a ramdrive. But this is rare.
And in any case - it still won't give a win against SSD.
Do not forget that any RAMdrive is a driver that is constantly spinning in RAM, and loads the processor quite heavily.

Answer 3

An SSD drive (the same M2) is fast enough to be quite comparable to a ramdisk in terms of speed.
You can push the browser with its cache onto the ramdisk, but the entire system with ALL programs does not make sense