Issue metadata
Sign in to add a comment
|
10.2% regression in cheets_VellamoTest/Browser_score on cros-veyron_minnie at 29490000907900001:29490000908100000 |
||||||||||||||||||||
Issue descriptionPerformance dashboard identified a 10.2% regression in cheets_VellamoTest/Browser_score on cros-veyron_minnie at revision range 29490000907900001:29490000908100000. Graph: https://chromeperf.appspot.com/report?masters=ARC&bots=cros-veyron_minnie&tests=cheets_VellamoTest%2FBrowser_score&checked=Browser_score%2CBrowser_score_ref%2Cref&rev=29490000908100000 Same regression on other platforms: https://chromeperf.appspot.com/report?sid=318a01485c8a8ed2fd61b7440df9092fade8eaf899930ed2999633d41f86130c&rev=29510000908700000 Since the regression seems to be happen on ChromeOS side (only ChromeOS uprev between two builds). Currently we don't have good tool for bisect between ChromeOS builds. I would like to write one for current use first and polish it and checkin into the repository in somewhere for sharing later on.
,
Mar 14 2017
Hi Luis, The bug is really old but the Vellemo score didn't come back since then so we are still hunting the root cause. Recently our automated bisection tool for Chrome OS repo is near complete and I decide to come back to old regressions using it for practice runs just like this. The Vellamo benchmark runs on Web View thus I think the regression is related to the WebView uprev changes in the list. The problem is that I am not familiar with WebViewGoogle development and have no idea where to track down what have been changed when it is uprevved to 55.0.2883.84 so I am seeking for your help. Please help confirm if the Vellamo score regression could be caused by the WebView uprev or not. If so, is it expected ? Thanks !
,
Mar 14 2017
,
Mar 14 2017
Yeah, it's definitely possible that it was caused by the uprev. The previous version was 53.0.2785.124, so _lots_ of stuff changed :/ https://chromium.googlesource.com/chromium/src/+log/53.0.2785.124..55.0.2883.84?pretty=fuller&n=10000
,
Mar 15 2017
I just downloaded the APK file and notice there is a libwebviewchromium.so inside, which is produced by the BUILD file in chromium_source/src/android_webview/. Guess doing the bisection only in chromium_source/src/android_webview/ would cause compatibility issues which looks unlikely working. Does that mean I have to do the bisection against all the changes (20K+ of them) between 53.0.2785.124 and 55.0.2883.84, generate WebViewGoogle APK file accordingly, update the APK file and the whole Chrome binaries and run the Vellamo test ? That's just quite insane. Let me think if there could be better ways to do so.
,
May 8 2017
,
Dec 12 2017
What's left? Can we close this?
,
Jan 7
,
Jan 8
|
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by hctsai@chromium.org
, Mar 14 2017