Restarting
Read restart recommendations.
We recommend restarting the NetCrunch Server service once a month to improve the system's performance.
We strongly recommend installing Microsoft updates and patches, so your whole system should also be restarted at least once per month.
NetCrunch includes an auto-restart feature that restarts its service on a given day and time. To change auto-restart parameters, go to: Settings NetCrunch System Maintenance. The shortest time between restarts is 1 day, and the longest is 100 days.
Why does restarting help to maintain healthy systems?
There are two main reasons why computers and systems do need to restart.
Fragmentation and resource cleanup
Memory Fragmentation
Even if the operating system uses algorithms that minimize the risk of fragmentation, it often happens. It manifests in an inability to allocate a large block of RAM. For example, the application must read a 10MB file to memory. The system might refuse to allocate the block despite having gigabytes of free memory. In such cases, the whole operating system must be restarted.
Resource Cleanup
The system has thousands of components, some of which leak resources. System resources are not limitless. This might be caused by the crashing process (process cleanup does not always claim 100% of resources) or a faulty DLL.
Restoring the proper state
In this case, programs or systems restart after the crash (i.e., blue screen BOD). The crash means that the program is in a state that does not allow further processing, which can lead to damage or unexpected behavior. In such cases, the code must be reinitialized into the proper state.
When such a problem occurs in any NetCrunch services (processes), they are automatically restarted, and the system continues running almost uninterrupted.