• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

How does Windows keep all the threads on the turbo'd cores?

It does by default I think? Just loads up threads sequentially.

What it cant do as yet is spread them around to make use of 'modules' , which I assume means lower clock speeds but hopefully (for AMD) spreading the load across shared parts of each module.
 
It does by default I think? Just loads up threads sequentially.

What it cant do as yet is spread them around to make use of 'modules' , which I assume means lower clock speeds but hopefully (for AMD) spreading the load across shared parts of each module.

So if you do a 32m superPi run without manually setting the core affinity, it sticks to the turbo'd cores? I thought Windows moved the thread around at high speed to even it out across the chip? Thermal reasons or something.
 
Back
Top