Thank you for providing your network file.
We have found the core issue of the problem.
HARK 2.5 only supported single thread processing, HARK 3.0 on the other hand now uses blas/openblas which allows multi threading.
The workload is spread over all the available CPU which caused the load you were experiencing.
Depending on the kind of process, the threads may not be efficiently used.
To reproduce the same load you had using HARK 2.5, please limit the process to a single thread.
This can be done by running the following command.
- This reply was modified 2 years, 9 months ago by c.santiago.