frostney / frostney/GocciaScript
Sub-5-minute test262 and throughput parity
Nobody has claimed this yet.
- Dominant language
- Pascal
- Stars
- 20
- Forks
- 3
- Avg merge
- 3d 4h
- Merged PRs (30d)
- 45
Description
Two goals: get the full test262 suite under 5 minutes (currently ~21.7 min — dominated by per-test process boot, so the lever is in-process engine reuse + lazy built-in boot, not tail-tuning), and reach throughput parity with reference embeddable engines on the common path (value unboxing, inline caches, collection hashing).
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 full test262 suite and measure the current per-test process boot cost against the approximately 21.7-minute baseline. Map the in-process engine reuse, lazy built-in boot, value unboxing, inline caches, and collection hashing areas, then verify that test262 runs under five minutes and common-path throughput reaches parity with reference embeddable engines.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- performance, testing-qa
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100