[pull] canary from vercel:canary - #1403
Merged
Merged
Conversation
## Summary - Store live meta files in primary per-family shards so queries avoid unrelated-family metadata - Consolidate live metadata during compaction, retire subsumed meta files in the same commit, and retain merged used-key-hash AMQFs. - Add debug assertions for shard ownership/order and compaction precedence invariants. ## Performance Paired `LARGE_DB=1` Criterion binaries were run interleaved on the same machine to reduce host drift. | Scenario | Canary | PR | Result | | --- | ---: | ---: | --- | | Four-family cached `get` miss (100 metas/family) | 2.40–2.55 µs | 2.11–2.21 µs | **~10–12% faster** | | Existing single-family cached `get` miss | 1.93–2.12 µs | 2.00–2.04 µs | Neutral within run-to-run noise (~+0.5% on means) | | Existing full compaction (4 Mi entries, 8 commits) | ~624 ms | ~624 ms | Neutral in the stable paired run; repeated samples stayed within normal noise | Read hits should see a small improvement but it isn't measurable, misses are the major benefit. ## Verification - `cargo test -p turbo-persistence` - `cargo test -p turbo-persistence --features stats` - `cargo clippy -p turbo-persistence --all-targets --features stats -- -D warnings` - `LARGE_DB=1` interleaved Criterion A/B runs <!-- NEXT_JS_LLM --> --------- Co-authored-by: vercel-fleet-prod[bot] <318278635+vercel-fleet-prod[bot]@users.noreply.github.com> Co-authored-by: Luke Sandberg <210140+lukesandberg@users.noreply.github.com>
## Summary Commit preview tarballs carry versions like `16.4.0-preview-84cee7e6-20260917` (no `canary` substring), so `isStableBuild()` treated them as stable and canary-only defaults (`turbopackSharedRuntime`, `turbopackMangleExportNames`) were disabled on what are canary-quality builds. Versions containing `-preview-` now count as unstable; numbered npm previews like `16.3.0-preview.10` stay stable. ## Verification - Added `canary-only-config-error.test.ts` covering the version matrix (fails on the tarball case without the fix) - `npx jest packages/next/src/server/config.test.ts` (existing consumer) passes <!-- NEXT_JS_LLM --> <!-- fleet ae573e35-b551-453d-af1c-548ffb598944 --> Co-authored-by: vercel-fleet-prod[bot] <318278635+vercel-fleet-prod[bot]@users.noreply.github.com>
) ## Summary The Bots and crawlers section in the caching guide said that all bots and crawlers skip the static shell because "they need a complete document". Only HTML-limited bots do, and the reason is metadata: with Partial Prerendering, `generateMetadata` can resolve dynamically and stream in after the shell, which puts the tags in the body rather than the `<head>`. Bots that need them in the `<head>` get a dynamic render instead. The second paragraph now states the consequence directly: if the build-time prerender read something unreachable at request time, the render throws and those bots get a 500. Which user agents this covers, and the `htmlLimitedBots` option for changing the list, stay owned by the Streaming guide, which the section links to. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
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.
See Commits and Changes for more details.
Created by
pull[bot] (v2.0.0-alpha.4)
Can you help keep this open source service alive? 💖 Please sponsor : )