https://github.com/didinj/quarkus-optimizing-performance-startuptime-memory-native-builds
Optimizing Quarkus Performance: Startup Time, Memory & Native Builds
https://github.com/didinj/quarkus-optimizing-performance-startuptime-memory-native-builds
backend java memory microservices native-builds optimizing-performance quarkus startup-time
Last synced: 22 days ago
JSON representation
Optimizing Quarkus Performance: Startup Time, Memory & Native Builds
- Host: GitHub
- URL: https://github.com/didinj/quarkus-optimizing-performance-startuptime-memory-native-builds
- Owner: didinj
- License: mit
- Created: 2025-11-20T08:39:53.000Z (6 months ago)
- Default Branch: main
- Last Pushed: 2025-11-20T11:40:24.000Z (6 months ago)
- Last Synced: 2025-11-20T13:18:01.442Z (6 months ago)
- Topics: backend, java, memory, microservices, native-builds, optimizing-performance, quarkus, startup-time
- Language: Java
- Homepage: https://www.djamware.com/post/691ed6c2f256430140070f22/optimizing-quarkus-performance-startup-time-memory-native-builds
- Size: 18.6 KB
- Stars: 0
- Watchers: 0
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# Optimizing Quarkus Performance: Startup Time, Memory & Native Builds
Read the full tutorial [here](https://www.djamware.com/post/691ed6c2f256430140070f22/optimizing-quarkus-performance-startup-time-memory-native-builds).
This project uses Quarkus, the Supersonic Subatomic Java Framework.
If you want to learn more about Quarkus, please visit its website: .
## Running the application in dev mode
You can run your application in dev mode that enables live coding using:
```shell script
./mvnw quarkus:dev
```
> **_NOTE:_** Quarkus now ships with a Dev UI, which is available in dev mode only at .
## Packaging and running the application
The application can be packaged using:
```shell script
./mvnw package
```
It produces the `quarkus-run.jar` file in the `target/quarkus-app/` directory.
Be aware that it’s not an _über-jar_ as the dependencies are copied into the `target/quarkus-app/lib/` directory.
The application is now runnable using `java -jar target/quarkus-app/quarkus-run.jar`.
If you want to build an _über-jar_, execute the following command:
```shell script
./mvnw package -Dquarkus.package.jar.type=uber-jar
```
The application, packaged as an _über-jar_, is now runnable using `java -jar target/*-runner.jar`.
## Creating a native executable
You can create a native executable using:
```shell script
./mvnw package -Dnative
```
Or, if you don't have GraalVM installed, you can run the native executable build in a container using:
```shell script
./mvnw package -Dnative -Dquarkus.native.container-build=true
```
You can then execute your native executable with: `./target/quarkus-performance-1.0.0-runner`
If you want to learn more about building native executables, please consult .
## Related Guides
- REST ([guide](https://quarkus.io/guides/rest)): A Jakarta REST implementation utilizing build time processing and Vert.x. This extension is not compatible with the quarkus-resteasy extension, or any of the extensions that depend on it.
- REST Jackson ([guide](https://quarkus.io/guides/rest#json-serialisation)): Jackson serialization support for Quarkus REST. This extension is not compatible with the quarkus-resteasy extension, or any of the extensions that depend on it
## Provided Code
### REST
Easily start your REST Web Services
[Related guide section...](https://quarkus.io/guides/getting-started-reactive#reactive-jax-rs-resources)