Insufficient hardware
Problem
Simulation Compute Manager or solvers crash unexpectedly on a machine that is running very slowly.
Cause
If a machine is pushed to the limits of its hardware capabilities (CPU or RAM), it is possible for the Simulation Compute Manager, or the solvers, to crash or behave unexpectedly. Forcing the system to use large amounts of swap memory is a known cause of significant performance degradation.
Symptoms
Analysis intermittently restarts, but never completes, and "HeartBeatTask","what":"Failed - send heartbeat Reason: Timeout;"
is present in the ComputeWorker.log file.
Simulation Compute Manager crashes during analysis, restarts a duplicate analysis, and "HeartBeatTask", "what": "Failed - send heartbeat Reason: Timeout;"
is present in the ComputeWorker.log file.
Analysis crashes with error ** ERROR 301150 ** Out of memory
.
Analysis progresses but is extremely slow.
What to do
Send analysis to a capable machine on the network using Simulation Compute Manager.
Send analysis to the cloud using Simulation Compute Manager.
Increase available memory by adding additional swap space.