Public result records
The result summaries name directory work, bridge requests and equal-work controls. Performance and responsiveness pages explain why those measurements cannot stand in for one another.
Compare equivalent work under documented conditions.
Computing-efficiency evaluations compare the same useful work under documented conditions. Read the workload definition, correctness checks, machine and runtime configuration before using a reported number to judge a system.
4,387,675Median mixed subsystem operations per second across three full-kernel runs, zero errors, 116 of 116 modules.
3.254×JRuby parallel scaling against 1.0005× CRuby scaling for equal checksum-matched work.
94,160,428Deterministic useful operations per second in the named maximum transport profile.
These published campaign summaries use different operation definitions. The figures below need their original run records for independent verification; they do not establish performance on another workload.
Correctness first
Equal work, checksums, postconditions, accepted samples, errors, and invalid-trial handling.
System context
Host, runtime, versions, topology, telemetry, startup boundaries, cleanup, and raw artifacts.
Limitations disclosed
Host and load dependence, mixed latency effects, energy scope, unreproduced claims, and experimental status.
Inspect the result, then the method.
A directory operation, an IPC request and a completed workload use different units. Read the record for the component and operation being measured before applying the result to another system.
Conditions, correctness and limits
Start with matched inputs and accepted output. Then inspect the environment, repeated trials and the boundary of the measurement, especially for energy claims.
Run a question against your workload
The Kestowv pilot references describe workload configuration and operating checks. They identify the supplied environment and the controls a repeatable evaluation needs.
The campaign figures above and the linked summaries cover separate tests. Request the original run record, configuration and correctness output before using a figure in an evaluation. The separately documented upstream contribution is available here: read the JRuby 10.1 contribution record.
Working through a hardware or runtime decision? Explore compute evaluations