Comment by extropy

The minimum run time of a tread before it's potentially preempted when load is high is computed based on number of cores available giving more time when there are more cores since rescheduling latency is apparently longer with more cores.

And the function that does this uses the same value for 8 and more cores.

So the performance impact is likely <<1%.