Originally posted by: ShadowOfMyself
Interesting links... Usually Id just pass them off as fud but since they have actual numbers to support it, now Im curious
I set out to reproduce this myself, and was able to do so. But... I also sort of discovered something else somewhat interesting along the way...
Results with four instances of CPU Burn In running quad core cpu at 100%:
PhysX FluidMark v1.0.0
[ SCORE: 1245 o3Marks ] - Time: 60000 ms
Res: 1920x1200 (FS) - MSAA: 4X
FPS: min=11 max=22 avg=21
Without CPU Burn in Running:
PhysX FluidMark v1.0.0
[ SCORE: 8161 o3Marks ] - Time: 60000 ms
Res: 1920x1200 (FS) - MSAA: 4X
FPS: min=93 max=342 avg=136
Without CPU Burn in running, looking at the CPU Usage History graph in Windows show core 0 running at 70-80% load during the FluidMark run.
Results with three instances of CPU Burn In running quad core cpu at ~77% (affinity 0,1,2):
PhysX FluidMark v1.0.0
[ SCORE: 1384 o3Marks ] - Time: 60000 ms
Res: 1920x1200 (FS) - MSAA: 4X
FPS: min=11 max=29 avg=23
Interestingly enough, core 3 doesn't show a significant increase in usage. Cores 0-2 were running at 100%, and core 3 was staying at ~10% during the entire benchmark, with a quick spike to 70%. So, I decided to try setting the affinity for CPU Burn In differently...
Results with three instances of CPU Burn In running quad core cpu at ~77% (affinity 1,2,3):
PhysX FluidMark v1.0.0
[ SCORE: 8124 o3Marks ] - Time: 60000 ms
Res: 1920x1200 (FS) - MSAA: 4X
FPS: min=102 max=343 avg=136
Hmmmm... interesting. This time core 0 was at 75-80% during the benchmark and cores 1-3 were all at 100%
Not sure what exactly to make of this, except that it looks like the benchmark might its affinity set to core 0.