4 ms·
Promising... but I'd wait for the real world benchmarks first. No one in the real world needs to emulate... geekbench.
by nottorp 6y ago
Promising... but I'd wait for the real world benchmarks first. No one in the real world needs to emulate... geekbench.
- hmottestad 6y agoWould be a lot worse if performance was 1/10th. That’s what this benchmark shows. Essentially that it’s a lot better than people feared. The question for users like myself is, will things like IntelliJ still be decently fast? Still don’t know what kind of performance we will get from the JVM, but this shows some decent hope!
- DonaldPShimoda 6y agoI imagine it won't take long for something as widely used as the JVM to be compiled directly for the M1 instead of relying on Rosetta. :)
- hmottestad 6y agoIronically Microsoft just released a beta arm version of the JVM for Mac.
- WoodenChair 6y ago> Ironically Microsoft just released a beta arm version of the JVM for Mac. I wasn't aware of this. Can you provide a link?
- lolpython 6y agohttps://appleinsider.com/articles/20/09/22/microsoft-contributes-to-java-port-for-apple-silicon-macs https://appleinsider.com/articles/20/09/22/microsoft-contrib...
- saagarjha 6y agoThey have, unfortunately it's a bit crashy in what looks new non-platform specific code.
- rbanffy 6y agoHow is that result with Windows on ARM laptops?
- p1necone 6y agoDoes the M1 deviate enough from standard ARM64 to need a recompile?
- DonaldPShimoda 6y agoOh! Probably not; that's a good point. I don't know why it didn't occur to me that, of course, there's already an ARM-compatible JVM haha. Thanks!
- wincy 6y agoWow I wonder if these new Macs are going to be the new standard for iOS and Android development, since you can run your apps for both ecosystems natively.
- chrisseaton 6y agoThe JVM is a bit lacking on ARM64. I’m still seeing super-basic intrinsics being added to the compilers.
- saagarjha 6y agoYes, it would need to be build for Darwin.
- DonaldPShimoda 6y agoGeekbench benchmarks provide evidence of an upper bound, which is useful for determining what is technically possible. Real-world benchmarks instead show what can be realistically observed. The upper bound benchmarks are still useful, just in a different way. For example: these benchmarks show that under excessive load (as benchmarks do), the M1 is capable of out-performing Intel chips at something like 1/3 the energy usage. No matter how you slice it, that is an impressive achievement and shows what M1 could potentially do for the most perfectly optimized software. Realistically, of course, software will not attain this. But having the upper bound lets software writers know what to aim for and when it's not worth pushing for extra performance.
- tambourine_man 6y agoGeekbench tries to simulate real world situations. HTML and PDF rendering, SQLite, etc https://www.geekbench.com/doc/geekbench5-cpu-workloads.pdf https://www.geekbench.com/doc/geekbench5-cpu-workloads.pdf
- hajile 6y agoHere's the "easily fits in cache" list * Compress a 2.3mb file that fits in cache. * Alter a 24MP JPEG (that's around 5MB filesize). * Gaussian blur of 24MP JPEG * Gumbo Parser of an HTML file then execute some stuff with duktape -- note: this parses HTML to a simple DOM -- nowhere close to actual rendering * Text rendering of 1,700 words into a 12MP image * Horizon detection of 9MP image (that's around 2MB) * Image repaint of 1MP image (that's around 200KB) * HDR image (4MP -- around 800KB) from 4 normal images * Neural Net of tiny 224x224 images * Navigate using a graph with 200k nodes and 450k edges. * SQLite is between 0.5MB and 1.1MB depending on the compiler options. Maybe the dataset pushes it out of cache, but I wouldn't bet on them creating many millions of rows. Not sure, but may not fit in cache * Google's PDFium render. Not sure about the library itself, but a 200dpi map doesn't sound like anything worth mentioning * Camera test gives very little in specifics, but with several steps and a handful of libraries, this probably overflows cache a little. * Ray Tracing 3.6K triangles and 768x768 output. I'd put it elsewhere, but they could be using a huge number of rays (though I seriously doubt it) Undoubtedly doesn't fit in cache * Clang rendering 730 LOC (seriously?) Clang is pretty big and most likely needs to cache. Zero actual details * Speech Recognition * N-Body Simulation * Rigid Body Simulation * Face Detection * Structure from Motion All in all, them saying these things are "real world" would be a huge overstatement at best. I don't see anything here to contradict Linus' assessment.
- tambourine_man 6y ago>All in all, them saying these things are "real world" would be a huge overstatement at best. What your list shows is that caches are huge these days. Because 24MP JPEGs are very much a real world scenario when most cameras sold in the world have half that resolution. But sure, go ahead and pick another industry standard benchmark of your choice. Let's see how the M1 fares.