Hi,
Problems like this can be tough to track down sometimes. Do you mind if I ask a few questions to establish what is happening?
- Are you working with the new Metrics view open? Note that keeping this view open does mean that NCrunch needs to keep it updated, so it will consume a bit more CPU.
- How large is your solution in approx lines of code and number of tests?
- Do you have heavy test saturation in your codebase? I.e. lines of code that are covered with at least several hundred tests
- When NCrunch takes a long time to process a test task, do you see this as reflected in the 'Processing time' against the test task in the processing queue? Or does the number seem much longer than it should be (given the sluggish speed)?
- Do the builds still run quickly?
Something else that can help provide more information is if you set your 'Log Verbosity' to 'Detailed' or 'Medium' under your NCrunch global configuration, along with turning on the 'Log to output window' setting. NCrunch should then start dropping large amounts of trace information in its output window. Performance problems can often show in the trace output as being steps inside the output that have large gaps between their timestamps. Look particularly for trace output against the 'Core' thread, for example:
[08:54:23.2835-Core-22] Publishing Event: [EngineModeSwitchedEvent:Run all tests automatically]
If you submit a bug report after a build/test cycle, I may be able to find the problem for you in the log file ... although it sounds as though your solution may be quite large, so the log file may not be very complete when it comes through.
