Re: [w3c/ServiceWorker] consider allowing multiple worker thread instances for a single registration (#756)

> We do have a metric (ServiceWorker.StartWorker.Purpose) that measures which event caused a SW start. I see ~6% of starts coming from message events vs. ~4% for Push delivery, ~30% for main-frame navigations, and a surprisingly high 53% for sub-resource fetches. Perhaps @mattto, @kinu, or @nhiroki can weigh in or shed more light.

I suspect long-running Facebook (and similar) tabs cause a large number of starts for subresources. The page periodically does a subresource request in the background at an interval greater than our idle timeout (30sec).

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/ServiceWorker/issues/756#issuecomment-243662819