3 ms·

I was an unbeliever, but we got some M1 Mac Mini's and this is the result. They even beat the dedicated workstation many of our people have set up. I get when p

I was an unbeliever, but we got some M1 Mac Mini's and this is the result. They even beat the dedicated workstation many of our people have set up. I get when people say it won't quite match a new ryzen for compute power, but in all of our tests, the M1 beat out all our workstations.

spockz 5y ago
What workloads do you run? I’ve got a 16GiB M1 mbp and a 2019 maxed intel and when compiling Java/sbt projects the intel is significantly quicker, albeit also much loader and power hungry.
- alienalp 5y ago
  That compiler most probably not native to m1 arm processor.
  - spockz 5y ago
    Indeed, I was using the GraalVM jdk11 build which wasn’t available in a native version indeed.
- alecthomas 5y ago
  As the sibling comment mentions, if you're running Intel JDK on M1 it will be slow. You can find M1 native JDK builds here: https://www.azul.com/downloads/?version=java-11-lts&os=macos&architecture=arm-64-bit&package=jdk https://www.azul.com/downloads/?version=java-11-lts&os=macos...
  - hugi 5y ago
    Just for fun, Oracle has also started providing natively compiled EA builds of JDK 17: https://jdk.java.net/17/ https://jdk.java.net/17/
- chrisseaton 5y ago
  > when compiling Java/sbt projects Are you comparing a binary being run under dynamic binary translation with a native binary? Not really an honest comparison, if that's the case.
  - formerly_proven 5y ago
    No idea if that's the case, but I wouldn't have expected Java of all things to be run under binary translation.
    - chrisseaton 5y ago
      > I wouldn't have expected Java of all things to be run under binary translation Why? The Java community has only just been working on ARM64 support at all over the last few years, and it's still a little limited, and macOS ARM64 support is only out a couple of weeks and only from non-Oracle third-party builders I believe.
    - nicoburns 5y ago
      > I wouldn't have expected Java of all things to be run under binary translation Depends which version you have installed. It's a taken a while for the native versions to reach the mainstream channels, so unless you've specifically installed an M1 build you probably have an x86 build being run under translation.
    - throwaway4good 5y ago
      You have to install a Java VM compiled for ARM such as the one made by Azul. If you just get the openjdk from the main website it is compiled for Intel and will be much slower.
    - biehl 5y ago
      Native support in the regular builds will arrive in september https://openjdk.java.net/projects/jdk/17/ https://openjdk.java.net/projects/jdk/17/
- spockz 5y ago
  Wow, based on the comments here I decided try out the native M1 builds of Azul. I see a 4.1x speedup in compiling (including tests), excluding dependency resolution: Azul Native M1 java JDK11: ./sbt "clean;compile;test:compile" 254.86s user 11.84s system 519% cpu 51.375 total Azul java JDK11: ./sbt "clean;compile;test:compile" 490.04s user 59.48s system 269% cpu 3:23.81 total

spockz 5y ago

What workloads do you run? I’ve got a 16GiB M1 mbp and a 2019 maxed intel and when compiling Java/sbt projects the intel is significantly quicker, albeit also much loader and power hungry.

alienalp 5y ago
That compiler most probably not native to m1 arm processor.
- spockz 5y ago
  Indeed, I was using the GraalVM jdk11 build which wasn’t available in a native version indeed.
alecthomas 5y ago
As the sibling comment mentions, if you're running Intel JDK on M1 it will be slow. You can find M1 native JDK builds here: https://www.azul.com/downloads/?version=java-11-lts&os=macos&architecture=arm-64-bit&package=jdk https://www.azul.com/downloads/?version=java-11-lts&os=macos...
- hugi 5y ago
  Just for fun, Oracle has also started providing natively compiled EA builds of JDK 17: https://jdk.java.net/17/ https://jdk.java.net/17/
chrisseaton 5y ago
> when compiling Java/sbt projects Are you comparing a binary being run under dynamic binary translation with a native binary? Not really an honest comparison, if that's the case.
- formerly_proven 5y ago
  No idea if that's the case, but I wouldn't have expected Java of all things to be run under binary translation.
  - chrisseaton 5y ago
    > I wouldn't have expected Java of all things to be run under binary translation Why? The Java community has only just been working on ARM64 support at all over the last few years, and it's still a little limited, and macOS ARM64 support is only out a couple of weeks and only from non-Oracle third-party builders I believe.
  - nicoburns 5y ago
    > I wouldn't have expected Java of all things to be run under binary translation Depends which version you have installed. It's a taken a while for the native versions to reach the mainstream channels, so unless you've specifically installed an M1 build you probably have an x86 build being run under translation.
  - throwaway4good 5y ago
    You have to install a Java VM compiled for ARM such as the one made by Azul. If you just get the openjdk from the main website it is compiled for Intel and will be much slower.
  - biehl 5y ago
    Native support in the regular builds will arrive in september https://openjdk.java.net/projects/jdk/17/ https://openjdk.java.net/projects/jdk/17/
spockz 5y ago
Wow, based on the comments here I decided try out the native M1 builds of Azul. I see a 4.1x speedup in compiling (including tests), excluding dependency resolution: Azul Native M1 java JDK11: ./sbt "clean;compile;test:compile" 254.86s user 11.84s system 519% cpu 51.375 total Azul java JDK11: ./sbt "clean;compile;test:compile" 490.04s user 59.48s system 269% cpu 3:23.81 total