[dexter1]

I've been doing some performance measurements with the mame 207 build and the emulated Indy PROM screen. First i've built the mame binary with the (in my opinion) fastest possible make command line options:

Code:

make -j5 SOURCES=src/mame/drivers/indy_indigo2.cpp REGENIE=1 TOOLS=1 OPTIMIZE=3 ARCHOPTS_C=-march=native ARCHOPTS_CXX=-march=native

I think OPTIMIZE is the correct keyword: i incorrectly mentioned OPTIMISE previously.
With the above make command i get about 19% on my Core i5-4590 CPU @ 3.30GHz.

Looking at 'perf top' in the linux-tools-generic package i record these functions and their percentage of cpu time:



So it looks like the R4000 core code in mame is taking about 60% of the total CPU time and if there is room for improvements, that would be the first place to start. I've tried with -drc and -nodrc and it didn't make any difference, so in infer that there is no dynamic recompile code active, which could potentially create lots of speed improvements.

We'll have to see what the future brings.