frostney / frostney/GocciaScript
Close the measured throughput gap on AWFY and web-tooling hotspots
Nobody has claimed this yet.
- Dominant language
- Pascal
- Stars
- 20
- Forks
- 3
- Avg merge
- 3d 4h
- Merged PRs (30d)
- 45
Description
Summary
Drive down the measured throughput gap on the Are We Fast Yet and web-tooling hotspots, prioritized by impact.
Why
Once the cross-engine harness (#856/#857) quantifies where GocciaScript trails reference embeddable engines, the remaining work is to close those specific hotspots — the concrete path to "viable embedding" throughput.
Current behavior
The gap is unquantified until the harness lands; the known structural levers are unboxing (#860) and inline caches (#861).
Expected behavior
- The per-benchmark gap on the worst AWFY / web-tooling cases is reduced to the target band and tracked over time.
Scope notes
- Depends on the harness (#856) and the structural levers (#860/#861). Parent #822.
Contributor 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.
Research direction
Start with the cross-engine harness in issues #856 and #857 once it lands, then use its per-benchmark results to identify the worst AWFY and web-tooling hotspots. Review the dependent unboxing and inline-cache work in #860 and #861; done means the worst gaps reach the target band and are tracked over time.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- performance
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100