GoogleChrome / GoogleChrome/lighthouse
Lantern: more accurate H2 simulation
- Dominant language
- JavaScript
- Stars
- 30.8k
- Forks
- 9.8k
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 20
Description
Right now the server response time isn't included per request and we really need 1 RTT per initiator
i.e. an asset is only "free" once we've incurred at least 1 RTT since all of their dependencies have been met
Complicated but would help accuracy on h2 simulation.
Contributor guide
Research direction
Start by locating the Lantern H2 simulation entry point and reviewing how dependency completion and request timing are currently modeled. Trace where per-request server response time and RTT assumptions would be represented. Done means the simulation applies one RTT per initiator before an asset becomes free and has coverage for the updated timing behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- networking, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100