Skip to content

Comparing the CPU/Memory utilisation - Quarkus via GraalVM Native Image vs. Quarkus via Java Runtime vs. Payara-Micro via Java Runtime.

License

Notifications You must be signed in to change notification settings

rmh78/quarkus-performance

Repository files navigation

Comparing the CPU/Memory utilisation of a REST service (Quarkus, Payara Micro, Spring Boot, Python)

Some scripts to measure the CPU and Memory utilisation of JAX-RS appliations. The performance test runs inside a docker container.

The test uses the following demo projects:

  • demo-payara contains a simple JAX-RS application packaged as uber-jar with Payara Micro (5.2020.4) application server
  • demo-payara-jpa contains an advanced JAX-RS, JSON-B, CDI, JPA, PostgresDB application packaged as uber-jar with Payara Micro (5.2020.4) application server
  • demo-quarkus contains a simple Quarkus (1.8.1.Final) application packaged as jar and additionally compiled as native image using the GraalVM Native Image
  • demo-quarkus-jpa contains an advanced JAX-RS, JSON-B, CDI, JPA, PostgresDB Quarkus (1.8.1.Final) application packaged as jar and additionally compiled as native image using the GraalVM Native Image
  • demo-python contains a simple (REST service) and advanced (REST with DB access) Python application
  • demo-spring-boot contains a simple REST service using Spring Boot (2.4.0-M3)
  • demo-spring-boot-jpa contains an advanced REST, JSON, JPA, PostgresDB service using Spring Boot (2.4.0-M3)

(1) Prepare and start plot-tests

  1. Modify the Dockerfile (look for PROXY) to use a proxy server or not
  2. Build the docker image with env_build.sh or env_build.cmd
  3. Run the image in a new docker container with env_run.sh or env_run.cmd
  4. Build the demo projects inside the docker container with ./scripts/build.sh
  5. Run the tests inside the docker container with ./scripts/test-all.sh
  6. Plots are generated to directory plots
  7. Logs are generated to directory logs

(2) Test scenario

The plot-test consists of the following actions:

  • starting the application (simple JAX-RS application)
  • wait until the first http request to the JAX-RS endpoint can be served (time to first request)
  • sleep 1 second
  • start load-test using apache benchmarking tool
    • requests: 5000
    • concurrency: 5
    • url: the JAX-RS endpoint of the application

(3) Plots

All plots are generated on my Notebook inside the running docker container.

Docker Host Machine:

  • CPU: Intel i7-8650U 1.90GHz (8 cores)
  • RAM: 16GB

Docker Engine Configuration:

  • CPUs: 4
  • Memory: 8 GB

(3.1) Quarkus via GraalVM Native Image

Simple Advanced

(3.2) Quarkus via Java Runtime

Simple Advanced

(3.3) Payara Micro via Java Runtime

Simple Advanced

(3.4) Spring Boot via GraalVM Native Image

Simple Advanced

(3.5) Spring Boot via Java Runtime

Simple Advanced

(3.6) Python

Simple Advanced

(4) Used Runtimes, Frameworks and Libraries

About

Comparing the CPU/Memory utilisation - Quarkus via GraalVM Native Image vs. Quarkus via Java Runtime vs. Payara-Micro via Java Runtime.

Topics

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published