Restore targeted placement to aws:us-east-1 - #1704
Merged
Merged
Conversation
Reverts the wrangler config change from #1693. Since that deploy user_store.getOrganization went from ~12ms to ~300ms p50 and mcp.auth.authorize_organization from ~70ms to ~400-700ms, which is the Worker no longer sharing a region with Hyperdrive.
Contributor
Cloudflare previewTorn down — the PR is closed. |
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
1 participant
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.
Reverts the wrangler config change from #1693.
Since that deploy (2026-08-19 15:07 UTC), per-deploy p50 keyed on
executor.commit_sha:user_store.getOrganizationworkos.userManagement.listOrganizationMembershipsmcp.auth.authorize_organizationworkos.session.local_verifyuser_store.*is Drizzle to Postgres over the HYPERDRIVE binding, and the placement pin existed since #420 specifically to co-locate the Worker with it, so the DB-side regression has a clear mechanism. The JWKS side moved the other way in the same window but is confounded by #1696 and #1697 landing within hours.Restoring the pin to measure the two effects independently. If the JWKS stall returns with it, that isolates the trade-off and points at fixing the JWKS cache directly rather than paying for it with placement.