Hi, thanks for posting.

Working with gigantic solution spaces is still a bit of a problem in NCrunch. To build test environments, NCrunch needs to have every relevant project in a dependency tree be loaded and built. This greatly limits our ability to work on only a subset of projects in a solution.

Have you tried using the 'Run impacted tests automatically, others manually' mode? This should greatly reduce the amount of work NCrunch needs to do when it spins up.

Beyond this, all I can suggest is to make smaller solutions. Perhaps you can have separate solutions that target different areas of your overall solution space. This would give a much better experience than using the ignore setting, as NCrunch wouldn't be throwing away all the test results and code coverage data every time you changed the setting. The "Ignore this component completely" setting isn't really designed to be turned on and off regularly throughout a session.