Skip to content

Add ops/CPU-sec metric to benchmarks - #1331

Merged
adwsingh merged 1 commit into
mainfrom
adwsingh/cpu-efficiency-metric
Aug 24, 2026
Merged

Add ops/CPU-sec metric to benchmarks#1331
adwsingh merged 1 commit into
mainfrom
adwsingh/cpu-efficiency-metric

Conversation

@adwsingh

@adwsingh adwsingh commented Aug 24, 2026

Copy link
Copy Markdown
Contributor

What behavior changes?

Serde JMH and live-service e2e benchmarks now report ops_per_cpu_sec, computed
from completed operations and process-wide CPU time. Converted JMH results fail
clearly if the metric is missing, and short e2e samples report it as unavailable.

Why is this change needed?

Add a CPU-efficiency metric alongside the existing benchmark latency and
throughput measurements.

How was this validated?

Added unit tests, ran all benchmark check tasks and formatting, and ran JDK 25
JMH smoke tests for RPC v2 CBOR and AWS JSON. Also verified the shaded JARs and
the missing-metric failure path.

What should reviewers focus on?

The process CPU-time boundaries, weighted JMH aggregation, and Gradle/Shadow
packaging of the shared profiler and generated service descriptors.

Additional Links

None.


By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@adwsingh adwsingh changed the title adwsingh/cpu efficiency metric Add ops/CPU-sec metric to benchmarks Aug 24, 2026
@adwsingh
adwsingh requested a review from mtdowling August 24, 2026 15:54
@adwsingh
adwsingh merged commit 065800a into main Aug 24, 2026
5 checks passed
@adwsingh
adwsingh deleted the adwsingh/cpu-efficiency-metric branch August 24, 2026 17:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants