Some good points, thanks for the insight :) Yeah, when I multithread something I pretty much assume that I can hog the whole machine for the time slice the job

Some good points, thanks for the insight :) Yeah, when I multithread something I pretty much assume that I can hog the whole machine for the time slice the job is going to be running. Said another way, I assume there will be a small number of large jobs running on the machine at any given time, which attempt to saturate the machine. Typically dispatched to a core-locked threadpool of some sort. Definitely agree with the sentiment that multithreading is hard. Especially when trying to get every last drop..