Visual Studio working with ramdisk, what's the problem?

Question

RAM

I start the project from a ramdisk, and the problem comes when the studio itself consumes 50% of the processor resources and lags the text editor. Who faced?

Answer 1

Alas, it’s a bummer, but neither an SSD nor a RAM disk significantly affects the build speed (sometimes there was a difference of about 10%, and all due to the fact that the files are still cached by the system and are in memory, in fact).
It makes sense to place *.pch and *.obj files on a RAM disk, leaving the project on the hard disk, while getting rid of unnecessary fragmentation.
When compiling, the studio "consumes" all 100% of all eight cores... When editing, the brakes appear only in the process of parsing the project and connected files (~ 2000 project files, plus all sorts of boosts and other nonsense).