Issue #5716
- p99
- 0.99ms
- failures
- 0%
- score
- 6,000.00
Closed May 20, 2026, 9:50 PM UTC by the upstream runner. Kept as accepted history, not current candidate state.
open issueA/B VARIANT // EVIDENCE TERMINAL
This static variant keeps the same brand system while testing denser proof above the fold: official upstream, current candidate CI, calibrated CI, runtime path, and source links before the archive.
RINHA 2026 // .NET 10 NATIVEAOT
A public proof dossier for a raw HTTP/1 fraud scorer: official upstream history, current CI candidate evidence, and the runtime path that keeps the hot loop small.
PROOF LEDGER
Every number below is lane-labeled. Official Rinha hardware remains separate from GitHub Actions and CPU-quota calibration.
Closed May 20, 2026, 9:50 PM UTC by the upstream runner. Kept as accepted history, not current candidate state.
open issueMain candidate at dc021e25a9a4. CI evidence only, but this is the current clean public artifact.
Projection lane for the same commit and workflow. It predicts pressure, it does not replace official hardware.
compare reportsLatest closed completed upstream issue authored by jonathanperis, synced through gh from zanfranceschi/rinha-de-backend-2026.
326 archived report rows across 157 candidate, 129 calibrated, and 40 experiment entries.
RUNTIME TRACE
The public boundary is the yolo load balancer, not ASP.NET Core.
The LB sends accepted client fds over Unix control sockets; APIs serve the client socket directly.
The app scans enough JSON to build the 14-dimensional fraud vector.
The default clean lane uses rounded int16 IVF plus repair; bucket/hybrid modes stay available for experiments.
The decision returns a small HTTP response without framework ceremony.
A/B TEST SURFACE
Default lane. Compare official, candidate, and calibrated proof above the fold.
review evidence laneMake provenance the lead object: issue, run, image, p99, failures, score.
review report ledgerLead with architecture: load balancer, sockets, parser, scorer, bytes.
review architecture laneCandidate metrics are local evidence from GitHub Actions. Official hardware is shown separately in the proof ledger.