Thanks. FWIW, Speedometer started with & always seemed like an Apple specific test. It greatly favors low optimization paths, because it's just loading app aft

Thanks. FWIW, Speedometer started with & always seemed like an Apple specific test. It greatly favors low optimization paths, because it's just loading app after app after app. It's basically not worth having optimizing compilers, because Speedometer is just testing initial load speed, more or less. That's a valid number, and I love that others (like Chrome) accept the thrown gauntlet as is, withiut protest, & compete. But this is not really indicative of what life will be like after the first 2s. Maps (or any other app) may run way way faster on an engine that focuses more on optimizing compilers. Thanks though, thanks for the links. Im not trying to invalidate this. But I do think it is limited, I do think it's origin & what it tests is worth noting in here. It's only one way of looking at performance.