Tools->Options->Monitoring->Advanced
->NetCrunch Monitoring Threads section
In general, the default settings should be left alone, but in some cases it might be necessary to change them.
Increasing monitoring performance
You can increase monitoring performance by changing thread settings if NetCrunch is running on a high-end machine dedicated exclusively to this monitoring application. For example, if the computer running NetCrunch has a limited number of resources (CPU, memory, etc.), you may change the thread allocation strategy to minimize the number of monitoring threads in the program.
Maximizing monitoring efficiency
If the computer with NetCrunch has plenty of extra resources, the setting can then be specified to maximize monitoring efficiency.
Thread count check time
The thread count check time specifies how often the monitoring thread management mechanism allocates or releases unused monitoring threads.
Decrease this number if you want NetCrunch to make such decisions more frequently at the price of greater computer resource utilization. Increasing this value decreases threads management to conserve precious resources such as CPU utilization.
Maximum number of monitoring threads
The maximum number of monitoring threads may be doubled or even tripled from the default value. In general, however, it should not be over 400. Increasing this setting is particularly useful when NetCrunch monitors many nodes running Windows operating system.
