[safe_browsing] Dispatch SafetyNet API request on a worker thread.
Recent data shows that the time it takes to dispatch the IPC to Google Play Services is quite expensive. Android canary data (so probably trends higher end), for the subresource filter check (in navigation critical path): 50th percentile: 6ms 75th percentile: 10ms 95th percentile: 28ms 99th percentile: 100ms Average: 11ms Since this is directly in the critical path of navigation, it makes sense not to hog the thread / deschedule it before the network request goes out. It also looks like we hit some perf issues in other uses of the API too. See the linked bug for some chrome://tracing traces. Bug: 779914 Change-Id: Ibc44d9f199715c3fbf7a2d66604e82ee3ccfc5e4 Reviewed-on: https://chromium-review.googlesource.com/760550 Commit-Queue: Charlie Harrison <csharrison@chromium.org> Reviewed-by:Varun Khaneja <vakh@chromium.org> Reviewed-by:
François Doray <fdoray@chromium.org> Cr-Commit-Position: refs/heads/master@{#517389}
Showing
Please register or sign in to comment