#SPEED20 XBENCH SCORE UPDATE#

clarify that the workload is scaled by cpu clock.emphasize the difference between the real time and the normalized time.

#SPEED20 XBENCH SCORE UPDATE#

Point 8 seems to be how the speed results are being recorded on the results repository.Īssuming this is correct, it would be helpful to update the readme to Because the clock speed factors cancel, the speed benchmark outputting unnormalized time ratios actually directly gives the per MHz information (assuming the baseline is 1MHz) so the real speed score can be obtained by multiplying the outputted speed by the clock of the board being used.This quantifies how much larger the embench speed score would be if the board was clocked 1MHz higher.

The embenches per MHz is the speed score with normalized times divided by MHz.

The speed benchmark program as is outputs unnormalized times in absolute mode and ratio of unnormalized baseline to unnormalized test chip in relative mode.

The embench speed score is the normalized time of the baseline divided by the normalized time of the chip being tested.

We normalize the real time by dividing by the MHz.

The goal is so each benchmark takes ~4s to run.

The real time taken by a benchmark is determined by the cycle count divided by the clock speed.

If the crc32 takes n cycles for a board at 1 MHz, it will take 2n cycles to run for a board at 2MHz.

Each benchmark is linearly scaled to the processor clock.

I am a little confused, but this is my understanding of the speed benchmark from the readme, results, and looking at past issues.

Speed20 xbench score