Skip to content

fix(eval): measure CPU time in Top-K ERP resources - #631

Merged
zzylol merged 2 commits into
eval/topk-dashboard-autosketchfrom
fix/topk-erp-cpu-units
Sep 11, 2026
Merged

fix(eval): measure CPU time in Top-K ERP resources#631
zzylol merged 2 commits into
eval/topk-dashboard-autosketchfrom
fix/topk-erp-cpu-units

Conversation

@zzylol

@zzylol zzylol commented Sep 11, 2026

Copy link
Copy Markdown
Contributor

The Top-K evaluation adapter wrote elapsed wall time into ERP *_cpu_seconds fields. Descheduling could therefore change a value presented as CPU cost, and existing catalogs could silently reuse those mislabeled measurements.

Calibration now reads the Linux process CPU clock for update, merge, and readout operations. Catalog provenance declares that time basis, and selection/reproduction reject old or missing CPU provenance. Generation and end-to-end query latency remain wall time. The historical v2 report is explicitly marked; its numbers are not replaced by invented corrected results.

Before this PR: wall-clock samples populated CPU resource fields and were accepted by ERP selection.

After this PR: only newly calibrated process-CPU evidence is accepted. Unsupported platforms fail explicitly rather than substituting elapsed time.

Verification: three focused Rust tests passed, including real sketch update/merge/readout CPU measurement and rejection of missing timing provenance. This fixes the offline adapter in #602; it does not establish a production control-plane comparison or new performance benefits. Full release recalibration remains pending.

@zzylol
zzylol marked this pull request as ready for review September 11, 2026 02:23
@zzylol
zzylol merged commit 301f833 into eval/topk-dashboard-autosketch Sep 11, 2026
1 check passed
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.

1 participant