1.39b is slugish

hello,

i've just installed the 1.39b ver with metrics and all the great stuff but unfortunately it is very slow :(

My solution consist of 17 projects (1 setup, 1 silverlights, 1 mvc3, 1 spec flow, 2 mb unit and some other plan c#) it looks like it takes ages to run the tests and in overall it looks like there is something bad happening under the hood. Any ideas how can I be helpful in diagnosing that ?

for now it looks like just the first run is very sluggish, then it works like it used to. I'll keep an eye on that

regards,

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.

Thanks - I just saw your later post as I finished off my own. It does make sense that the first run-through would seem slightly longer, as 1.39b caches some additional information during its first trip through your codebase. If you continue to notice sluggishness, please let me know. This release should be much faster than the others (indeed I went through considerable pain to make it so).

- Are you working with the new Metrics view open?

YES, ofc :) its a killer :)

- How large is your solution in approx lines of code and number of tests?
NCrunch says its ~16k

- Do you have heavy test saturation in your codebase? I.e. lines of code that are covered with at least several hundred tests
~800 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)?
hm.. i dont quite understand the question

- Do the builds still run quickly?
it looks for me like the build time of one of the projects was very slow but I'm not to sure about that, i'll keep an eye for that


(indeed I went through considerable pain to make it so).
The pain you wend through gave some awesome results that brought a lot of joy, WOWs and lots of warm words for you in my team (and a bit of envy that there is such a guy that writes such an awesome stuff all by itself).

best regards