In our setup we have multiple processes. The application that we are benchmarking itself, plus our the process that generates the load plus any optional depende

In our setup we have multiple processes. The application that we are benchmarking itself, plus our the process that generates the load plus any optional dependencies of the application. These all are scheduled over the number of cores of the docker vm. From the outside it is hard to track which internal process was scheduled where.