Thanks for the numbers! -- it looks like a native ARM app would be a definite advantage for most tasks - see below...

There seem to be two different types of MCM1 jobs, one showing VMethod=NFCV in its parameters, the other showing VMethod=LOO. On my Intel and Ryzen machines, NFCV tasks seem to take from 25% longer (Ryzen, with extra FP pathways!) up to over twice as long to run (Intel Kaby Lake), and something equivalent may be playing out with your numbers on the Pi4 (though it's a much bigger difference than the ones I've seen on native applications.)

When they ran the last MCM1 beta, I snagged a few on my Pi4, and the LOO ones typically took about 4.25 to 4.5 hours (3 at a time, 2GHz clock.) Given the lack of L3 cache and the relatively slow clock compared to my "traditional" machines, I reckon comparing that against around 1.75 hours on an i5-7600 or i7-7700K or around 1.6 hours on a Ryzen 3700X isn't too bad!!! Unfortunately, I have no recorded times for NFCV tasks on the Pi4 :-(

By the way, the beta more or less equalized the run-times of NFCV and LOO tasks on Intel and Ryzen - if anything, the NFCV tasks were now a bit quicker than the LOO tasks. Whether this would also apply on the Pi remains to be seen, as [according to perf stat anallysis done on the production application on various platforms] NFCV appears to make more calls on L3 cache per instruction executed than LOO does, and the lack of such cache may affect timings. ,

Given the above, I'd repeat my plea to the WCC technicians - please can we have an ARM version of MCM1? If that Beta test was anything to go by, it would make far better use of my Pi4 than does OPN1 (with its much higher amount of L2 cache misses!)

Cheers - Al.