Hi, thanks for posting.

Looking at the details you've posted, my bet here would be that the issue is memory related. When the system runs out of available memory, the IDE will start to perform very poorly. In this case, it's probably giving NCrunch the blame for the typing lag because it's the only thing in the stack other than VS itself.

Which processes are contributing to high memory consumption? Do you have any particularly hungry tests?

With the info you've shared, I think that having only 8GB available for VS, NCrunch, and all your tests is probably not sufficient for the size of your solution.

5 years ago 16GB was easily enough, but these days even a single open website can eat 300MB.

The platform is eating more RAM too. I've noticed that the build system under VS2022 consumes around 4x as much memory as it did under VS2019. Now that VS2022 is also running under x64, the process will consume more memory, and we can expect this to grow rapidly now that MS are not restricted by the 3GB LAA x86 limit.

With a lot of careful configuration and a great deal of pain, you might be able to reduce your memory consumption to the point where you can work without lag again, but you'll be fighting a losing battle. In the long term, buying more RAM is your only real option here.



We do have a setting that might help with this (test process memory limit).