GCM registration / unregistration is inconsistently slow and can take ~3 seconds
Reported by
ja...@onesignal.com,
Mar 31 2016
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.110 Safari/537.36 Steps to reproduce the problem: 1. Visit https://onesignal.com/serviceworker-subscribe.html 2. Open chrome://gcm-internals and click Start Recording. 3. Open the Console and click the "Register Service Worker, Subscribe, and Unsubscribe" button. The button can be clicked again and again. What is the expected behavior? GCM registration and unregistration requests should take take less time to complete and be more consistent with the time taken to complete. What went wrong? Looking at the chrome://gcm-internals page, it looks like the registration and unregistration requests take varying amounts of time to complete. Sometimes it is consistently 3 seconds from request to response. Sometimes, it is instant (time reported can sometimes show 0.01 seconds). Did this work before? No Chrome version: 49.0.2623.110 Channel: stable OS Version: OS X 10.11.1 Flash Version: Shockwave Flash 21.0 r0 What could be affecting this, and could the timings be improved?
,
Apr 1 2016
Creating a subscription hits the network, so I'm not surprised that there are differences here. Requests completed in 0.01 seconds seem oddly fast. Looking at metrics we record for connection times to GCM (which is not the same as creating a registration, but at least related), three seconds actually happens to be the 90th percentile. We could add further metrics specific to the registration operation, but I'm not convinced it'll gain us much. John, what do you think?
,
Apr 12 2016
Marking this as Available and untagging OS=Mac.
,
Apr 12 2016
We already have a histogram for registration time (GCM.RegistrationCompleteTime, only measured on non-Android). It shows a bimodal distribution, with most registrations taking 100-700 ms, but with a spike around 3 seconds. I mentioned it to the GCM team; they're working on resolving some latency issues, which will hopefully improve things. I don't think there's anything further we can do from our end, though if it gets worse we should reopen this. |
||||
►
Sign in to add a comment |
||||
Comment 1 by rsesek@chromium.org
, Apr 1 2016