New issue
Advanced search Search tips

Issue 852202 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Jul 12
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Task

Blocking:
issue 846235



Sign in to add a comment

Performance analysis of NetS13nServiceWorker

Project Member Reported by shimazu@chromium.org, Jun 13 2018

Issue description

Implementation of NetS13nServiceWorker is progressing, and now it mostly works.
Let's measure the performance and get the performance insights.
 
Issue 846235 is tracking the implementation.

Comment 2 by falken@chromium.org, Jun 13 2018

Blocking: 846235
Project Member

Comment 4 by 42576172...@developer.gserviceaccount.com, Jun 13 2018

📍 Job complete. See results below.
https://pinpoint-dot-chromeperf.appspot.com/job/11c34885240000
Regarding to the result of pinpoint, I couldn't read any reliable performance insights from there.

I looked at timeToFirstContentfulPaint by splitting into "stories" and "cache_temperatureTag", and FlipKart::hot with NetS13nSW was slightly better but it's in the range of stdev. DevOpera results are in very wide range, so I don't think it's reliable.

So, I think we can conclude that we don't have obvious and significant regressions for now. Let's revisit the performance after starting experiment in wild.

Comment 7 by dxie@google.com, Jun 19 2018

Labels: Hotlist-KnownIssue
Status: Fixed (was: Started)
We did local testing and fixed major issues.
 issue 856521 : serving cached meta data
 issue 854902 : avoiding thread hop to the main thread

In the next step, let's see the performance in wild.

Sign in to add a comment