fastify +0.62% after optimization round 1: by-name reads on family objects take generic slow paths
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- rust, typescript
- Domain
- backend, performance
Research direction
Start by reading the optimization round 1 PR and the referenced /root/claude-p2opt/PROGRESS.md, then trace by-name reads through native_get::try_data_lookup_key and the get-by-name tail. Use the fastify inject instructions:u witness to measure the holey family layout paths. Done means by-name reads on family objects use the layout or probe and the reported generic slow-path costs improve.
Written by the indexing model from the issue text.
Description
Fix-forward for the optimization round 1 PR. C1/C2 make some fastify classes family objects; their by-name reads (native_get::try_data_lookup_key, the get-by-name tail) take generic slow paths on the holey family layouts: family_own_key +35M, read_own +16M, object_keys_and_live_slot_count +25M, keys_find_slot_by_bytes +13M (partly offset by chain_admits_add −35M). Fix: answer by-name reads on family objects from the layout or the probe. Witness: fastify inject instructions:u. Attribution: perrymaster /root/claude-p2opt/PROGRESS.md.
- Dominant language
- Rust
- Stars
- 4.9k
- Forks
- 166
- Avg merge
- 3h 23m
- Merged PRs (30d)
- 911
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from PerryTS/perry
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 1 day
-
bug
Difficulty 3/5 1-2 days Newbie friendliness 67/100
Maintainers usually reply within 1 day
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 76/100
Maintainers usually reply within 1 day
Similar issues
-
area:desktop priority:p2 type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
fritzprix/libr-agent#2165 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 69/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
area:ecosystem bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Chelis-Lang/chelis#3942 ·
Maintainers usually reply within 1 day