Record the production verification of the CPU fixes - #33
Merged
Conversation
Deployed to studyplanner-api from main (version e355b6c8) after PR #32. The backend tree on main is byte-identical to the branch the staging measurements were taken on, so production runs exactly what was tested. On production, on a verified-fresh isolate, period=all survived 120 rounds where it previously died after five. Twenty concurrent users completed 400/400 requests on a catalog session and 480/480 on a session that also includes /api/me/progress, favorites, semester-plans and completed-courses -- the authenticated half could only be exercised here, since staging cannot validate production-minted sessions. The health gate passes after the load with no isolate left wedged. That is the result that matters: this load used to leave permanently dead isolates behind, which is what users saw as everything failing for them while other users were fine. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Deploying studyplaner with
|
| Latest commit: |
48e01e2
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://0c7c9b58.studyplaner.pages.dev |
| Branch Preview URL: | https://docs-production-load-test-ve.studyplaner.pages.dev |
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.
Follow-up to #32, which is now deployed to
studyplanner-apifrommain(versione355b6c8).Documentation only — no code change.
Verified on production
Üintact, no replacement charsperiod=all, verified-fresh isolate (seq=6)/api/me/*The last row is the one that matters. Before the fix this load reliably left permanently dead isolates behind, which is what users experienced as "everything fails for me but works for everyone else".
The authenticated half of the session could only be exercised on production, because staging cannot validate production-minted sessions — the two Workers have separate
AUTH_TOKEN_SECRETs.The backend tree on
mainis byte-identical to the branch the staging measurements were taken on, so production runs exactly what was tested; the other commits onmainare frontend-only.🤖 Generated with Claude Code