Branch Misprediction

[Siekmanski]

I usually follow the RDTSC route, today I followed the method inherited from the other thread which has also some advantages, in my opinion.

:t

The timers are not to calculate routine execution times.
These timers are meant to run simultaneous in realtime to control multimedia events in games or demos.

for example:

- timer 1 controls the time to switch to the next scene.
- timer 2 controls when a flock of birds fly over.
- timer 3 controls the duration of a bullet salvo.
- timer 4 controls when an UFO enters the earth orbit.

etc.

[LordAdef]

Hi jose, Thanks for carrying the tourch!

Code Select Expand

Unpredictable Branching Performance Test using xorshift32 begins:

Test A (Branching):  1452.756573     esi: 100007857

Test B (No Branching/Using SETCC):  679.610210     esi: 99997780

Test C (No Branching/Using CMOV):  588.437494     esi: 100011413

Press any key to continue ...


[daydreamer]

The timers are not to calculate routine execution times.
These timers are meant to run simultaneous in realtime to control multimedia events in games or demos.

for example:

- timer 1 controls the time to switch to the next scene.
- timer 2 controls when a flock of birds fly over.
- timer 3 controls the duration of a bullet salvo.
- timer 4 controls when an UFO enters the earth orbit.

etc.

I look forward to test timers for synchronize several threads working together
LOCK prefix maybe needs to be used?
rdrand vs simplest randomgenerator used in perlin noise would be interesting to test against each other
I think we should add D nobranch test:SIMD comparisions so we know how much worth the time spending on getting nonbranch code right and how much gain/loss?