Skip to content

Commit 1bcbed4

Browse files
committed
initial performance check in
1 parent 45a5acd commit 1bcbed4

File tree

3 files changed

+31
-0
lines changed

3 files changed

+31
-0
lines changed

_includes/performance.html

Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,17 @@
1+
<div class="full-width-bg component">
2+
<div class="grid-wrapper">
3+
<div class="width-12-12 width-12-12-m">
4+
<h2>The Quarkus Way</h2>
5+
<p>Quarkus redefines Java development by shifting most framework optimizations to the build phase. This approach minimizes runtime dependencies, maximizes dead code elimination, and introduces clear metadata contracts, resulting in leaner and more efficient applications.</p>
6+
<p>By performing these optimizations at build time, Quarkus ensures that the heavy lifting is done once, not at every startup, reducing memory usage and startup time.</p>
7+
<p>This approach benefits both GraalVM native images and traditional HotSpot JVM deployments, leading to faster, smaller, and more resource-efficient Java applications.</p>
8+
<h2>Reduced Memory</h2>
9+
<p>Quarkus reduces memory utilization for both traditional JVM deployments as well as native binaries using Ahead-of-Time (AOT) Compilation with GraalVM. It achieves this by leveraging build-time metadata processing, which shifts much of the runtime work to build time, lowering memory consumption during execution.</p>
10+
<h2>Fast Startup Time</h2>
11+
<p>Quarkus delivers fast startup times that allow for automatic scaling up and down of microservices on containers or Kubernetes deployments. It achieves fast startup times by performing build-time processing for both JVM and native binary deployments, reducing the work done during runtime. Quarkus precomputes metadata and optimizes class loading, significantly cutting down on initialization time. For natively compiled binaries, Quarkus uses GraalVM to eliminate startup overhead resulting in near-instant startup times by running directly as a native executable.</p>
12+
<h2>Disk Footprint</h2>
13+
<p>Quarkus reduces the footprint of Java applications by employing build-time processing to eliminate unnecessary runtime dependencies and by optimizing the application’s deployment artifacts. It packages only the essential classes and resources needed at runtime, removing unused code through techniques like dead code elimination. When using GraalVM for native compilation, Quarkus further reduces the footprint by compiling the application into a compact native binary, stripping out the JVM and related dependencies.</p>
14+
</div>
15+
</div>
16+
</div>
17+

_layouts/performance.html

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,7 @@
1+
---
2+
layout: base
3+
---
4+
5+
{% include title-band.html %}
6+
7+
{% include performance.html %}

performance.md

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,7 @@
1+
---
2+
layout: performance
3+
title: Quarkus Performance
4+
subtitle: Designed for speed and efficiency with minimal footprint.
5+
permalink: /performance/
6+
---
7+

0 commit comments

Comments
 (0)