This is quite a pleasant surprise considering how power-efficient Apple M1 is. We notice projects with big speed gain like Element Android have sequential build tasks including code linting, security scanning, and Gradle tasks. To answer the question: Gradle Profiler was used to run build profiling.

You may ask why build performance gain is massive on some but insignificant on others.

Java 17 on M1 gives the best build performance among others.

Therefore, upgrading to Java 17 is a no-brainer as your projects get built faster for free.

Java 17 offers decent optimization over Java 11, the gain can be observed on both Linux and macOS platforms.

Java 11 on M1 is not optimized for Apple silicon as it runs in Rosetta 2, which is subpar.

There’s a huge difference in terms of performance between Java 11 and Java 17 on Apple silicon.

Key findings about Java 11 vs Java 17 performance on M1 machines:

Learn more about building your Flutter app faster with M1.

💡TIP: You can also build Flutter apps on M1 machines to experience faster build times. The time diff * and credit diff * are calculated from Linux stack and Apple M1 stack because they give the most valuable insight. Comparing the credit usage between Linux machines and Apple M1 machines

M1 android studio