-
-
Notifications
You must be signed in to change notification settings - Fork 161
perf(runtime): compact an owned keys array in place on delete (populated delete −26.8%) #9013
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,32 @@ | ||
| `delete obj[k]` stops allocating when the keys array is owned. | ||
|
|
||
| The delete cloned the keys array unconditionally, because one array is shared | ||
| by every object that built the shape through a `transition_cache_lookup` hit — | ||
| mutating it in place would drop entries from siblings that never deleted | ||
| anything. | ||
|
|
||
| Sharing is tracked, though: the caches stamp `GC_FLAG_SHAPE_SHARED` when they | ||
| publish an array, and both the ordinary `[[Set]]` growth path and | ||
| `object_ops::keys_array` already treat that bit as authoritative for exactly | ||
| this clone-or-mutate decision. An array without it has a single owner and can | ||
| be compacted in place, which removes the last per-delete allocation here — a | ||
| ~500-element clone, 200k of them on `bench_populated_delete.ts` — and keeps | ||
| the array's address, so the key index needs only a slot shift rather than a | ||
| migration to a new id. | ||
|
|
||
| **The shape must be re-published** for the same array at its new key count. | ||
| Without that the object keeps a stamped ShapeId whose descriptor still claims | ||
| the pre-delete count, and the shape-facts audit catches it outright | ||
| ("published ShapeId disagrees with authoritative ObjectHeader facts") — an | ||
| earlier version of this change failed precisely there. | ||
| `publish_object_shape_from` versions a same-pointer change internally, and | ||
| `keys_changed` is false, so the typed layout is preserved rather than marked | ||
| unknown. | ||
|
|
||
| Interleaved A/B, min-of-13 at quiet load (~1.0): `bench_populated_delete` | ||
| 2768 → **2026 ms, −26.8%** (mean −27.0%). Combined overwrite and | ||
| realistic-name read unchanged. | ||
|
|
||
| Cumulative this session: **5938 → 2026 ms, −65.9%**, i.e. ~280× node → ~96×. | ||
| Suite 2788 passed, no warnings; adversarial property differential and | ||
| computed-key differential both byte-identical to node. | ||
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win
Use one release-note entry.
These lines describe development history, internal implementation details, and benchmark-session results. Reduce the fragment to one concise statement of the shipped behavior.
Based on learnings: “describe the final shipped behavior as one coherent release-note entry” and do not include separate development-slice narratives.
🤖 Prompt for AI Agents
Source: Learnings