WordPress / WordPress/performance
Investigate extended lifetime shared workers for sending URL Metric data
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 461
- Forks
- 165
- Avg merge
- 11h 12m
- Merged PRs (30d)
- 28
Description
Feature Description
There is a new extended lifetime shared workers currently in origin trial in Chrome. It allows for logic to run after a page has unloaded, for up to 30 seconds. This would be an alternative to the current approach implemented in #1893 via #1959 which keeps re-compressing URL Metric data whenever it is changed so that at the moment the page is closed, the pagehide event will be able to send the data without needing to invoke an asynchronous API to compress the data, which then often prevents the data from ever being sent in the beacon.
Related:
- #1970
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 by reading the current approach in #1893 and #1959, then review the extended lifetime shared workers origin-trial behavior described in the Chrome link. Compare it with the pagehide-based URL Metric sending flow and related issue #1970; done means determining whether shared workers are a viable alternative and documenting the findings.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- performance, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100