[VHRanger]

Visual studio is slow because its an unoptimized piece of software (it misses CPU cache often and does frequent disk seeks, etc.)

The best way to get performance from such software is:

1) make sure it (and the project) are on a fast SSD. NVME is better but SATA is good.

2) getting a good CPU for the workload. For pure IDE user experience it won't make much of a difference as long as it's a recent high end enough CPU (fast RAM latency, high enough clock frequency, enough cores, ...)

[chiph]

Also make sure that the TEMP/TMP folders are on the SSD.

[mrlonglong]

Nope, that'll eat precious NAND blocks on that SSD, eke out that endurance by putting your temp folders in a ramdisk if you can spare the memory.

[chiph]

I have come to accept that I will be replacing SSDs periodically. Either because they're worn out, or because a newer/faster/better technology is available.

A RAM disk is an interesting alternative for sure. The last time I used one was when I did OS/2 development using IBM VisualAge IDE. Which sorely needed it...

Windows doesn't have a driver for one out of the box, but there is a freeware one named ImDisk that looks widely used.

Thanks for mental nudge.

[fomine3]

NAND blocks aren't precious now. Just buy large reliable SSD (may have around 500TBW) and just forget it.