The Rust port roughly halved CPU per request and doubled HTTP throughput versus Oracle native. This checklist is for the agent running the tests: verify each item on the current Quarkus native build in e1, measure before and after, and report numbers in the same format as the jvm-native-rust report.
Confirm whether Quarkus HTTP request handling uses virtual threads (JDK 21+) or a fixed platform thread pool. Check quarkus.http.so-reuse-port / executor config, thread dump under load, and /q/metrics or actuator endpoints if exposed.
The jvm-native-rust report noted the JVM gRPC thread pool (30 threads) exhausted around 1.6 cores at ~1,683 rps. Native may inherit a similar pool. Check the gRPC executor configuration and bump it or route gRPC through the virtual-thread executor.
At 6,000 rps even small per-request allocations matter. Profile with GraalVM Native Image's built-in allocation sampling or async-profiler.
G1GC is already in use with ~1% of one CPU and 1–2 ms pauses. Still worth confirming pause distribution and frequency under the new higher load from items 1–3.
If each request opens or borrows connections expensively, pooling matters at high concurrency. Check the AWS SDK client config: max connections, acquire timeout, and whether HTTP/2 is enabled.
Quarkus on native uses Netty. Check whether the event loop is the bottleneck versus worker threads — CPU profile should show where time goes when HTTP rps plateaus.
After applying changes, re-run JVM, Oracle native, and Rust side by side on 2-CPU pods exactly as on 18 Oct, with identical load generators and the same 1,000 compared calls for response equality.
Context: Rust port did the same work (DynamoDB reads, segments-admin cache, Univex evaluation, metrics) and returned identical responses. Fairness notes from that run still apply. This checklist targets only the Quarkus native side.