Skip to content

Resume benchmarks without repeatedly exporting completed cases - #8

Merged
haksunli merged 3 commits into
mainfrom
fix/fast-benchmark-resume
Nov 4, 2026
Merged

haksunli merged 3 commits into
mainfrom
fix/fast-benchmark-resume

Conversation

@haksunli

@haksunli haksunli commented Nov 4, 2026

Copy link
Copy Markdown
Contributor

Resuming a run previously re-entered every completed case, regenerated aggregate reports and recompressed the complete results ZIP repeatedly. Application 1.3.1 verifies saved fork pairs in one scan, restores their results in case order, and enters the measurement loop only for unfinished or corrupt cases. Completed cases keep their original fork/checkpoint files. Fork checkpoints remain immediate and synchronized; ZIP exports are limited to once a minute with forced completion/interruption snapshots. Short Windows AccessDenied rename failures are retried without deleting the previous file or ignoring write failures.

Add an explicit -UpgradeResume PowerShell option for stopped published 1.3.0 runs. The helper requires the exact original release SHA-256, locks and backs up the request, and byte-compares the two applications, allowing only audited resume/export classes, its added helper and application version metadata. Numerical harness sources, dependency classes, case-model class and other launcher classes must match. Only the application fingerprint is migrated, with provenance; normal configuration/binary/machine checks and fork checksums remain enforced. Without the option, existing runs retain their original runner automatically.

Validation: 16 local launcher tests, including checkpoint preservation, stable case ordering, 640 suppressed ZIP refreshes, forced final export and refusal of changed numerical/dependency content. CI checks Windows/Linux all-library smoke, fast resume with no completed-case loop, and a real published 1.3.0 upgrade with unchanged fork hashes before publication. Benchmark inputs, algorithms, case plan, JMH timing settings and comparison dependency pins are unchanged.

@haksunli
haksunli merged commit 3f59d9f into main Nov 4, 2026
6 checks 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