Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Member
Author
|
Closing this draft after exact-source provider qualification measured a regression: 24 billed CPU-minutes versus 20 for original main, with slower Ready and longer post-ready cache work. The branch remains available as a rejected experiment; cache-only work will be qualified separately. |
This branch was successfully deployed
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.
This draft tested compiling the shared hosted API implementation once while retaining ten separate entrypoints, canonical paths, query handling, rewrites, 60-second limits, and independent limiter instances.
The source and local checks were sound:
bun run check:apipassed 49 tests / 621 assertions; workflow coverage passed 35 tests / 1,056 assertions; exact local response, render, cleanup, and limiter-boundary checks passed; and the hosted Preview exposed all ten functions with the expected public status checks.The exact-source hosted cost qualification rejects this candidate for production. The original main deployment
dpl_3tqjLvBbzxL6H9tZc1YTDwPWcsWUused 245.238 seconds of container time and 20 billed CPU-minutes, reached Ready in 108.926 seconds, and spent 136.312 seconds in post-ready cache work. The candidate18783aa2a69b6438c50ad9eabadb2ce55cc17e31used 313.679 seconds, 24 billed CPU-minutes, reached Ready in 121.554 seconds, and spent 192.125 seconds post-ready. This is a measured regression, so there is no production rollout or savings claim.The branch is retained as a reproducible rejected experiment. Any future cache-only qualification must use the original production source separately from this compiler change.