bench: add hosted MCP workload proof - #307
Merged
Merged
Conversation
lbliii
marked this pull request as ready for review
July 10, 2026 00:20
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Add the first mergeable slice of #229: an artifact-ready, real-Milo MCP workload plus Pounce-owned transport proof.
tools/callworkload alternating a pure-Python CPU tool and a blocking toolCLI.asgi_app()under Pounce, Uvicorn, Hypercorn, or Granian through the existing Epic: Benchmark evidence program — sustained load, p99, published artifacts #228 artifact pipeline--ratepath instead of silently sending a different request through wrk/hey--workload allbehavior unless the fixed-rate driver is selectedProgresses #229. This deliberately does not close the epic.
Dependency and deployment blockers
The workload uses Milo's public
CLI.asgi_app()from milo-cli#127. Until that draft stack merges and releases, install that branch in the benchmark environment; the benchmark app fails with an actionable message on older Milo releases.The existing Railway
pounce-railway-smokeservice is healthy and remains untouched. #229's Milo MCP deployment should be a separate service rather than repurposing the production canary; provisioning that service is intentionally deferred pending explicit infrastructure/cost approval and the Milo release.Milo #107 still owns the end-user Railway/Cloud Run/Fly recipes. Pounce #248 already supplies the free-threaded Railway
$PORT/healthcheck base those recipes can copy.Proof
ty check src/pounce/: cleanPYTHON_GIL=0: the local Milo Investigate and add a measured sendfile minimum-size threshold so tiny static files skip transport-detach overhead #127 app completed the alternating workload under both Pounce and Uvicorn with no request errorsbenchmarks/artifact-schema.json; no local number is promoted as a public claimPerformance note
No Pounce parser, worker, scheduler, framing, or request-pipeline hot path changed. The implementation is benchmark-driver and fixture code only, so no before/after runtime benchmark is required. Short local runs validated executability and artifact shape; publishable comparison numbers still require the repeated hosted 3.14/process and 3.14t/thread matrix described by #229.
Steward notes