New issue
Advanced search Search tips

Issue 661759 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Dec 2016
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug



Sign in to add a comment

SafeBrowsing->GMSCore latency increased in M54

Project Member Reported by nparker@chromium.org, Nov 2 2016

Issue description

SB2.RemoteCall.Elapsed increased as follows:

5th%: 7->9%
50th%: 20->31ms
95th%: 140->210ms

It showed up on M54-dev on Aug 9, then later on M54 Beta, now recently on Stable. It appears to have landed just after M53 was branched.
https://uma.googleplex.com/timeline_v2?sid=96db1b09f8509b0ef4bf362dc5a6d83f
I can't find evidence it's affecting page load time, but I suspect it is since SB2.Delay also increased at the 95%th.

I think that bounds the CLs to the range 53.0.2785.44 -> 54.0.2823.2 though the following link seems to cover a month.
https://chromium.googlesource.com/chromium/src/+log/53.0.2785.0..54.0.2823.0?pretty=fuller&n=10000

 

Comment 1 by vakh@chromium.org, Nov 4 2016

Labels: SafeBrowsing-Triaged
Status: Fixed (was: Assigned)
This is fixed in https://chrome-internal-review.googlesource.com/#/c/305595/ and merged to M56.

Sign in to add a comment