I have a problem running a large number of CircDBG instances in parallel on a cluster because I cannot control resource usage. Config parameter ThreadsNum doesn't seem to work for me, as I use your examplefrom README with 4 threads, and some processes easily take 25 cores on the cluster. Memory sometimes goes above 65GB with no increase in CPU usage. As a result, the cluster is brought into heavy swapping and remains unresponsive for hours.
Am I doing something wrong? Is there a way to predict resource usage so I can pan execution with SLURM?
If I were to put a hard limit on the CircDBG container such as 40GB, what would happen to that process?
Thanks!
I have a problem running a large number of CircDBG instances in parallel on a cluster because I cannot control resource usage. Config parameter ThreadsNum doesn't seem to work for me, as I use your examplefrom README with 4 threads, and some processes easily take 25 cores on the cluster. Memory sometimes goes above 65GB with no increase in CPU usage. As a result, the cluster is brought into heavy swapping and remains unresponsive for hours.
Am I doing something wrong? Is there a way to predict resource usage so I can pan execution with SLURM?
If I were to put a hard limit on the CircDBG container such as 40GB, what would happen to that process?
Thanks!