> BTW, given that you're benchmarking in a noisy multi-tasking environment, I'd
> generally pick the maximum value over three runs rather than the average.
> You'll probably never actually achieve the real maximum speed, but the more runs you
> do, statistically you'll probably get a max that starts to approach it.
> By averaging, all you need is one ill-timed bit of background activity to create an
> artifically bad score that will disappear the next time you run.
Good point. I've attached a spreadsheet with my updated benchmarks taking the highest of three runs for each game in the benchmark.
Still "-bench 90" with the official MAME 0.192 64-bit executable as before.
GroovyMAME support forum on BYOAC