Skip to content

fix(runtime): meter interactive programs in-module like standalone runs #95

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
JacobLinCool merged 3 commits into from
Oct 7, 2026
Merged

fix(runtime): meter interactive programs in-module like standalone runs #95

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
2c95913
fix(runtime): meter interactive programs exactly like standalone runs
TakalaWang Oct 6, 2026
b99b588
perf(runtime): meter interactive programs in-module like standalone runs
TakalaWang Oct 6, 2026
92baeb3
Merge main into interactive metering fix; preserve Python interactor …
JacobLinCool Oct 7, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,6 +6,13 @@ All notable changes to WASM-OJ are recorded here. Releases follow

## Unreleased

- Interactive contestants and interactors now use the same in-module instruction meter as
standalone runs, and the runtime reads each program's counter when it exits. They are charged
exactly what a standalone run charges for the same code; the previous host meter left out the
meter's own per-block cost, so tight loops cost up to 11 times less. They also run as fast as
standalone runs; a tight loop used to run about 18 times slower under `interact`, so CPU-bound
contestants hit the wall deadline before their instruction budget. Interactive costs rise to the
standalone values, and the refreshed runtime identity changes cost profiles.
- Accept runtime-bundle interactors (for example CPython) in `Runner.interact` on the server
and in the browser runner Worker. Either side of an interactive session may now be a
standalone Wasm module or a runtime bundle that provides streaming fd 0.
Expand Down
Loading