test(cache): add App Router Response Store load harness - #3299
Draft
james-elicx wants to merge 3 commits into
Draft
james-elicx wants to merge 3 commits into
james-elicx wants to merge 3 commits into
Conversation
@vinext/cloudflare
create-vinext-app
@vinext/types
vinext
@cloudflare/workers-response-store
commit: |
james-elicx
marked this pull request as draft
September 15, 2026 17:24
Contributor
|
Contributor
Performance benchmarksCompared 0 improved · 0 regressed · 6 within ±1.5%
View detailed results and traces 🟢 improvement · 🔴 regression · ⚫ change below 1.5% · paired base/head |
Member
Author
|
Closing because this load experiment was not requested as a pull request. The harness and result work will continue locally. |
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.
Scenario
This adds an isolated vinext App Router load-test app for the production Workers Response Store path. It intentionally uses unique route IDs so each lifecycle starts from a cold key rather than measuring an already-warm Workers Cache hit.
Cacheable lifecycle
/cacheable/:id, an App Router page forced to render at runtime.next.config.mjsappliesCache-Control: public, s-maxage=15, stale-while-revalidate=15only to this route.MISSon the first request, then the same render token on a storedHIT.UPDATINGwith the old token, then polls until a recoveredHIThas a new token.Dynamic lifecycle
/dynamic/:idtwice at the same URL.force-dynamicwith no public cache-policy override.no-store, neither reportsHIT/UPDATING, and each render has a different token.Load shape and output
The in-directory README documents prerequisites, one-time bucket creation, build/deploy ordering, smoke and high-load commands, every runner option, JSON fields, and CSV export for charting.
Observed App Router experiment
Durable Object is overloaded. Requests queued for too long.The generated experiment JSON and graph artifacts are not committed.
Validation
node --check examples/response-store-demo/load-test/load.mjsgit diff --check