I am running a simulation with 50000 pythia8 events using
o2-sim -m PIPE ITS MFT -j16 -e TGeant3 -g pythia8 -n 50000 on alidock.
It started using 100% of all CPU cores for at least the first couple thousand events. Now it is a bit over midway, at about event # 35000, and the CPU load is consistently at 50%. workerlog0 has several lines of
BUSY WAITING SIZE. The first occurrence appeared at event # 8861.
Since Detector.h says that
"this should ideally never happen", I report it here. I can share the logs if necessary.
A couple of weeks ago I ran similar simulation with the full ALICE setup, on Ubuntu 18.04 docker container. It also presented the same slowdown midway, but I did not investigate. Looking back at the logs,
BUSY WAITING SIZE is there, starting at event 17233.
By the way, workerlog0 has the combined output of all workers. I wonder if is there any way to discriminate each worker on the logs?