Potential busywait caused by Pacing
Evaluations with TUM revealed that if pacing is enabled, their test suite stops working in the following way:
- One peer stops receiving data.
- On this peer, the load of one CPU goes up to 100%.
This needs further investigation as setting pacingEnabled to false solved the problem.