New Features for the ServiceWorker Performance

[sisidovski]

Session description

The session is going to be a presentation part and discussion part.

In the TPAC 2023 breakout, the Google Chrome browser team shared recent efforts on ServiceWorker and discussed potential opportunities for making ServiceWorker even faster. This year, we’d like to present a couple of updates from last year, including a newly shipped feature called Static Routing API, the new proposal extending Resource Timing API for the Static Routing API, and some of future ideas like or ServiceWorkerAutoPreload.

For the first half of the session, we’re going to present performance problems around ServiceWorker and introduce new APIs and how it works. For the second half, we’d like to spend time on the discussion.

Session goal

This session aims to discuss ServiceWorkers performance issues, and how we can mitigate them. For the static routing API (now it’s part of the ServiceWorker spec), we’d like to hear browser vender status. For the other APIs that we’re proposing, we’d like to discuss and gather feedback from the community to make the standardization process forward.

Additional session chairs (Optional)

@quasi-mod

Who can attend

Anyone may attend (Default)

IRC channel (Optional)

#serviceworkers

Other sessions where we should avoid scheduling conflicts (Optional)

No response

Instructions for meeting planners (Optional)

No response

Agenda for the meeting.

No response

Links to calendar

• 2024-09-25, 11:15 - 12:15

Meeting materials

• Slides
• Minutes

[tpac-breakout-bot]

Thank you for proposing a session!

You may update the session description as needed and at any time before the meeting, but please keep in mind that tooling relies on issue formatting: follow the instructions and leave all headings and other formatting intact in particular. Bots and W3C meeting organizers may also update the description, to fix formatting issues or add links and other relevant information. Please do not revert these changes. Feel free to use comments to raise questions.

Do not expect formal approval; W3C meeting organizers endeavor to schedule all proposed sessions that are in scope for a breakout. Actual scheduling should take place shortly before the meeting.