good to know....i have 6 so its not an issue.....but still good to know
This issue can be experienced with any number of cores above 1. It's caused by the program getting moved to execution on different cores which had the overhead of transferring program state between cores' personal L1/L2 caches. However, it should also be very uncommon, as the task scheduler for any OS tries to minimize exactly that occurrence, and does so very successfully for most single-threaded programs (including UrT).