Think I need to look into this command to the CPU Affinity.

Locks a process to a particular core.


  prefix="taskset -c 1",

CPU Affinity

CPU affinity is a scheduler property that “bonds” a process to a given set of CPUs on the system.

This didn’t really fix the issue. At the end of the day, the scheduler is smart enough to determine which cpu to give the load.

NO, taskset is very useful for isolation.

So you know exactly how many cores a process needs to run properly at full speed.