Copilot commented on code in PR #13755:
URL: https://github.com/apache/skywalking/pull/13755#discussion_r2975111736
##########
docs/en/setup/backend/graalvm-distro.md:
##########
@@ -0,0 +1,59 @@
+# GraalVM Native Image Distribution
+
+Apache SkyWalking provides an alternative distribution built with GraalVM
native image, delivered as a
+self-contained binary with faster startup and lower memory footprint.
+
+## Why Choose the GraalVM Distro
+
+| Aspect | Standard OAP (JVM)
| GraalVM Distro |
+|--------------------------------------|--------------------------------------------|----------------------------|
+| Startup | Seconds to minutes
| Instant |
+| Memory | 1 GB+ heap typical
| ~512 MB |
+| Artifact | JARs + JVM required
| ~203 MB single binary |
+| Storage backends | BanyanDB, Elasticsearch, MySQL,
PostgreSQL | BanyanDB only |
+| Module set | Dynamically loaded via SPI
| Fixed at build time |
+| DSL rules (OAL, MAL, LAL, Hierarchy) | Compiled at startup
| Pre-compiled at build time |
+
+Benchmark results (Apple M3 Max, BanyanDB backend, 20 RPS sustained load):
+
+| Metric | Standard OAP (JVM) | GraalVM Distro | Improvement |
+|----------------------|--------------------|----------------|---------------|
+| Cold boot | 635 ms | 5 ms | ~127x faster |
+| Memory (idle) | ~1.2 GiB | ~41 MiB | 97% reduction |
+| Memory (20 RPS) | 2,068 MiB | 629 MiB | 70% reduction |
+| CPU (median, 20 RPS) | 101 millicores | 68 millicores | 33% reduction |
+| Throughput | Baseline | Identical | No difference |
+
+See the [full benchmark blog
post](https://skywalking.apache.org/blog/2026-03-13-skywalking-graalvm-distro-design-and-benchmarks/)
for details.
+
+The GraalVM distro is a good fit when you want:
+
+- **Container-friendly deployments** with minimal image size and instant
readiness.
+- **Lower resource usage** for small-to-medium scale environments.
+- **BanyanDB as your storage backend**, which is already the recommended
default.
+
+## Limitations
+
+- **BanyanDB is the sole supported storage backend.** Elasticsearch, MySQL,
and PostgreSQL are not available.
+- **Modules are selected at build time.** Runtime SPI discovery is not
supported.
+- **DSL rules are pre-compiled at build time.** Dynamic rule changes require
rebuilding the binary.
+
+All existing SkyWalking agents, UI, and CLI tools remain fully compatible.
+
+## Download
+
+Pre-built binaries are available for Linux (AMD64/ARM64) and macOS (ARM64) on
the
+[SkyWalking
Downloads](https://skywalking.apache.org/downloads/#SkyWalkingGraalVMDistro)
page.
+
+Docker images are also available on GHCR.
+
+## Version Mapping
+
+Each GraalVM distro release corresponds to a specific SkyWalking OAP version.
+See the [version mapping
table](https://skywalking.apache.org/docs/skywalking-graalvm-distro/next/version-mapping/)
+for the exact correspondence.
+
+## Documentation
+
+For setup instructions, configuration details, and the full documentation,
refer to the
+[SkyWalking GraalVM Distro
documentation](https://skywalking.apache.org/docs/skywalking-graalvm-distro/latest/readme/).
Review Comment:
This page is placed under Setup > Quick Start, but unlike the other Quick
Start pages (e.g., backend-setup/docker/k8s) it doesn’t end with a "What's
Next" section that points readers to the Marketplace/next steps. Consider
adding the same closing section for consistency and navigation.
```suggestion
[SkyWalking GraalVM Distro
documentation](https://skywalking.apache.org/docs/skywalking-graalvm-distro/latest/readme/).
## What's Next
- Proceed with backend deployment using your preferred option (Docker,
Kubernetes, or other).
- Explore available extensions and integrations in the SkyWalking
Marketplace and related documentation to tailor your deployment.
```
##########
docs/en/setup/backend/graalvm-distro.md:
##########
@@ -0,0 +1,59 @@
+# GraalVM Native Image Distribution
+
+Apache SkyWalking provides an alternative distribution built with GraalVM
native image, delivered as a
+self-contained binary with faster startup and lower memory footprint.
+
+## Why Choose the GraalVM Distro
+
+| Aspect | Standard OAP (JVM)
| GraalVM Distro |
+|--------------------------------------|--------------------------------------------|----------------------------|
+| Startup | Seconds to minutes
| Instant |
+| Memory | 1 GB+ heap typical
| ~512 MB |
+| Artifact | JARs + JVM required
| ~203 MB single binary |
+| Storage backends | BanyanDB, Elasticsearch, MySQL,
PostgreSQL | BanyanDB only |
+| Module set | Dynamically loaded via SPI
| Fixed at build time |
+| DSL rules (OAL, MAL, LAL, Hierarchy) | Compiled at startup
| Pre-compiled at build time |
+
+Benchmark results (Apple M3 Max, BanyanDB backend, 20 RPS sustained load):
Review Comment:
The "Startup" row claims the JVM OAP starts in "Seconds to minutes", but the
benchmark table below lists a 635 ms cold boot for the same Standard OAP.
Consider aligning the wording (e.g., describe typical startup ranges, or
clarify that the benchmark uses a minimized/configured setup) to avoid
contradictory guidance on this page.
```suggestion
| Aspect | Standard OAP (JVM)
| GraalVM Distro |
|--------------------------------------|--------------------------------------------------------|----------------------------|
| Startup | Typically seconds to minutes (can
be faster when tuned) | Instant |
| Memory | 1 GB+ heap typical
| ~512 MB |
| Artifact | JARs + JVM required
| ~203 MB single binary |
| Storage backends | BanyanDB, Elasticsearch, MySQL,
PostgreSQL | BanyanDB only |
| Module set | Dynamically loaded via SPI
| Fixed at build time |
| DSL rules (OAL, MAL, LAL, Hierarchy) | Compiled at startup
| Pre-compiled at build time |
Benchmark results for a tuned setup (Apple M3 Max, BanyanDB backend, 20 RPS
sustained load):
```
##########
docs/en/setup/backend/graalvm-distro.md:
##########
@@ -0,0 +1,59 @@
+# GraalVM Native Image Distribution
+
+Apache SkyWalking provides an alternative distribution built with GraalVM
native image, delivered as a
+self-contained binary with faster startup and lower memory footprint.
+
+## Why Choose the GraalVM Distro
+
+| Aspect | Standard OAP (JVM)
| GraalVM Distro |
+|--------------------------------------|--------------------------------------------|----------------------------|
+| Startup | Seconds to minutes
| Instant |
+| Memory | 1 GB+ heap typical
| ~512 MB |
+| Artifact | JARs + JVM required
| ~203 MB single binary |
+| Storage backends | BanyanDB, Elasticsearch, MySQL,
PostgreSQL | BanyanDB only |
+| Module set | Dynamically loaded via SPI
| Fixed at build time |
+| DSL rules (OAL, MAL, LAL, Hierarchy) | Compiled at startup
| Pre-compiled at build time |
+
+Benchmark results (Apple M3 Max, BanyanDB backend, 20 RPS sustained load):
+
+| Metric | Standard OAP (JVM) | GraalVM Distro | Improvement |
+|----------------------|--------------------|----------------|---------------|
+| Cold boot | 635 ms | 5 ms | ~127x faster |
+| Memory (idle) | ~1.2 GiB | ~41 MiB | 97% reduction |
+| Memory (20 RPS) | 2,068 MiB | 629 MiB | 70% reduction |
+| CPU (median, 20 RPS) | 101 millicores | 68 millicores | 33% reduction |
+| Throughput | Baseline | Identical | No difference |
+
+See the [full benchmark blog
post](https://skywalking.apache.org/blog/2026-03-13-skywalking-graalvm-distro-design-and-benchmarks/)
for details.
+
+The GraalVM distro is a good fit when you want:
+
+- **Container-friendly deployments** with minimal image size and instant
readiness.
+- **Lower resource usage** for small-to-medium scale environments.
+- **BanyanDB as your storage backend**, which is already the recommended
default.
+
+## Limitations
+
+- **BanyanDB is the sole supported storage backend.** Elasticsearch, MySQL,
and PostgreSQL are not available.
+- **Modules are selected at build time.** Runtime SPI discovery is not
supported.
+- **DSL rules are pre-compiled at build time.** Dynamic rule changes require
rebuilding the binary.
+
+All existing SkyWalking agents, UI, and CLI tools remain fully compatible.
+
+## Download
+
+Pre-built binaries are available for Linux (AMD64/ARM64) and macOS (ARM64) on
the
+[SkyWalking
Downloads](https://skywalking.apache.org/downloads/#SkyWalkingGraalVMDistro)
page.
+
+Docker images are also available on GHCR.
Review Comment:
"Docker images are also available on GHCR" is hard to act on because it
doesn’t link to the image repository/tag naming. Please add a direct link to
the relevant GHCR package (and ideally the image name users should pull).
```suggestion
Docker images are also available on GHCR as
[`ghcr.io/apache/skywalking-oap-server-graalvm-distro`](https://github.com/apache/skywalking/pkgs/container/skywalking-oap-server-graalvm-distro)
(for example: `docker pull
ghcr.io/apache/skywalking-oap-server-graalvm-distro:<version>`).
```
##########
docs/en/setup/backend/graalvm-distro.md:
##########
@@ -0,0 +1,59 @@
+# GraalVM Native Image Distribution
+
+Apache SkyWalking provides an alternative distribution built with GraalVM
native image, delivered as a
+self-contained binary with faster startup and lower memory footprint.
+
+## Why Choose the GraalVM Distro
+
+| Aspect | Standard OAP (JVM)
| GraalVM Distro |
+|--------------------------------------|--------------------------------------------|----------------------------|
+| Startup | Seconds to minutes
| Instant |
+| Memory | 1 GB+ heap typical
| ~512 MB |
+| Artifact | JARs + JVM required
| ~203 MB single binary |
+| Storage backends | BanyanDB, Elasticsearch, MySQL,
PostgreSQL | BanyanDB only |
+| Module set | Dynamically loaded via SPI
| Fixed at build time |
+| DSL rules (OAL, MAL, LAL, Hierarchy) | Compiled at startup
| Pre-compiled at build time |
+
+Benchmark results (Apple M3 Max, BanyanDB backend, 20 RPS sustained load):
+
+| Metric | Standard OAP (JVM) | GraalVM Distro | Improvement |
+|----------------------|--------------------|----------------|---------------|
+| Cold boot | 635 ms | 5 ms | ~127x faster |
+| Memory (idle) | ~1.2 GiB | ~41 MiB | 97% reduction |
+| Memory (20 RPS) | 2,068 MiB | 629 MiB | 70% reduction |
+| CPU (median, 20 RPS) | 101 millicores | 68 millicores | 33% reduction |
+| Throughput | Baseline | Identical | No difference |
+
+See the [full benchmark blog
post](https://skywalking.apache.org/blog/2026-03-13-skywalking-graalvm-distro-design-and-benchmarks/)
for details.
+
+The GraalVM distro is a good fit when you want:
+
+- **Container-friendly deployments** with minimal image size and instant
readiness.
+- **Lower resource usage** for small-to-medium scale environments.
+- **BanyanDB as your storage backend**, which is already the recommended
default.
+
+## Limitations
+
+- **BanyanDB is the sole supported storage backend.** Elasticsearch, MySQL,
and PostgreSQL are not available.
+- **Modules are selected at build time.** Runtime SPI discovery is not
supported.
+- **DSL rules are pre-compiled at build time.** Dynamic rule changes require
rebuilding the binary.
+
+All existing SkyWalking agents, UI, and CLI tools remain fully compatible.
+
+## Download
+
+Pre-built binaries are available for Linux (AMD64/ARM64) and macOS (ARM64) on
the
+[SkyWalking
Downloads](https://skywalking.apache.org/downloads/#SkyWalkingGraalVMDistro)
page.
+
+Docker images are also available on GHCR.
+
+## Version Mapping
+
+Each GraalVM distro release corresponds to a specific SkyWalking OAP version.
+See the [version mapping
table](https://skywalking.apache.org/docs/skywalking-graalvm-distro/next/version-mapping/)
+for the exact correspondence.
+
+## Documentation
+
+For setup instructions, configuration details, and the full documentation,
refer to the
+[SkyWalking GraalVM Distro
documentation](https://skywalking.apache.org/docs/skywalking-graalvm-distro/latest/readme/).
Review Comment:
The external doc links mix "/next/" (version mapping) and "/latest/"
(readme). This can send readers to mismatched versions of the GraalVM distro
docs. Please make these links consistent (choose either "latest" for stable
docs, or "next" if this page targets the unreleased doc set) and ensure the
intent is clear.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
