Click the button below to start a new development environment:
β οΈ All measurements are highly dependent on the characteristics of my computer. So feel free to replay the commands to make up your own mind.
We use the time
command to measure performance (execution time and memory consumption).
The use of this command differs depending on whether you're running MacOS or Linux :
- MacOS
$ TIMEFMT+=' %M kb rss'
$ time <COMMAND>
#0,00s user 0,00s system 0% cpu 1,014 total 1168 kb rss
- Linux
$ /usr/bin/time -f "%E real,%U user,%S sys, %M kb rss" <COMMAND>
#01.03 real,0.00 user,0.00 sys, 1648 kb rss
In the output of the time
command, there are 2 elements of interest to us :
- Program execution time (
real
ortotal
) -><VALUE> real
or<VALUE> total
Startup Time = Program Execution Time - Solution Time
- Solution Time : Time taken for user code to be executed
- Program Execution Time: Total program run time (runtime startup time + Solution Time)
- Memory consumption of the executed program ->
<VALUE> kb rss
- Basic compilation in Java ππΌ How the JIT Compiler works
- GraalVM JIT Compiler ππΌ Installing and testing GraalVM JIT
- GraalVM AOT Compiler ππΌ Discover the Ahead Of Time (AOT) compilation with GraalVM
- Spring Boot Native - AOT ππΌ Discover the Ahead Of Time (AOT) compilation with Spring Boot + GraalVM
- Quarkus Native - AOT ππΌ Discover the Ahead Of Time (AOT) compilation with Quarkus + GraalVM
- CLI with Quarkus Native - AOT ππΌ Discover the Ahead Of Time (AOT) compilation with Quarkus + GraalVM + Picocli