New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 789207 link

Starred by 1 user
Status: Fixed
Owner:
█ ranj@chromium.org
Last visit > 30 days ago
Closed: Dec 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Android
Pri: 2
Type: Bug



Sign in to add a comment

Test install speed of v2 signing

Project Member Reported by yfried...@chromium.org, Nov 28 2017 
V2 signing has been published to chrome canary for a little over a week now. The server takes ~1s extra to mint because we haven't implmented go signing. We were advised that we expect client-side install latency to go down (vs v1 signing) but it doesn't appear that there's much benefit or at least it may be washed out by server time.

Before we completely put this to bed, and rule out the server latency we can do some local testing of pure client side installation time.

Basically on a low-end device for a few popular webapks:
1) get a copy for canary channel (v2 signing)
2) get a copy for dev channel (v1 signing)
3) install each 10-20 times measuring install latency (as many as necessary to get tight bounds)

Confirm that there's no negligible improvement.

Comment 1 by ranj@chromium.org, Nov 29 2017 

Tested on my Nexus 5X

Downloaded Chrome Canary and Dev through play store, install Twitter Lite, pull out and install again through adb, the time for adb install to finish is:

V2:
1.514s, 1.408s, 1.604s, 1.475s, 1.653s, 1.449s, 1.593s, 1.565s, 1.569s, 1.431s, 1.426s, 1.635s, 1.518s, 1.473s, 1.489s, 1.418s, 1.391s, 1.401s, 1.446s, 1.509s
Average: 1.49835s

V1:
1.404s, 1.496s, 1.469s, 1.461s, 1.474s, 1.457s, 1.398s, 1.409s, 1.581s, 1.439s, 1.405s, 1.465s, 1.358s, 1.562s, 1.561s, 1.496s, 1.558s, 1.472s, 1.443s, 1.587s
Average: 1.47475s

The time is very consistent between V2 and V1

Comment 2 by yfried...@chromium.org, Nov 29 2017 

Nexus 5x is still not that low end. Can you try our galaxy jprime?

Comment 3 by ranj@chromium.org, Dec 4 2017 

Tested on jprime

V2:
1.854s,1.837s,1.302s,1.755s,2.196s,1.814s,1.794s,1.831s,1.805s,1.795s,1.916s,1.771s,1.919s,1.833s,1.854s
Average: 1.8184s

V1:
1.968s,1.795s,1.790s,1.849s,1.861s,1.946s,1.741s,1.893s,1.816s,1.750s,1.913s,1.749s,1.871s,1.840s,1.897s
Average: 1.845s


The result is still very close.

Comment 4 by ranj@chromium.org, Dec 4 2017

Status: Fixed (was: Assigned)
►

Sign in to add a comment