Add Web Components page sets and benchmark

Add Web Components page sets and benchmark

Add a benchmark for measuring loading metrics for applications which use
Web Components.

The page set contains only sample shopping application in Polymer 2. We have a plan
to add more pages and stories.

Now the benchmark is using loadingMetrics as is. That could be changed in the
future.

BUG=703996

[hayato, 2017-02-17 08:07:15]

The CQ bit was checked by hayato@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2017-02-17 08:07:34]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2017-02-17 09:55:09]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2017-02-17 09:55:10]

Dry run: This issue passed the CQ dry run.

[hayato, 2017-03-21 05:59:11]

WIP:

[hayato, 2017-03-22 06:24:28]

WIP:

[hayato, 2017-03-30 05:30:57]

wip

[hayato, 2017-03-30 05:30:58]

The CQ bit was checked by hayato@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2017-03-30 05:31:10]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[hayato, 2017-03-30 05:43:13]

wip

[hayato, 2017-03-30 05:43:15]

The CQ bit was checked by hayato@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2017-03-30 05:43:38]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[hayato, 2017-03-30 05:56:23]

Description was changed from

==========
wip: shadow dom perf test

BUG=
==========

to

==========
Add Web Components page sets and benchmark

Add a benchmark for measuring loading metrics for applications which use
Web Components.

The page set contains only sample shopping application in Polymer 2. We have a
plan
to add more pages and stories.

Now the benchmark is using loadingMetrics as is. That could be changed in the
future.

BUG=703996
==========

[hayato, 2017-03-30 05:56:23]

hayato@chromium.org changed reviewers:
+ nednguyen@google.com

[hayato, 2017-03-30 05:56:56]

PTAL

[nednguyen, 2017-03-30 07:06:15]

On 2017/03/30 05:56:56, hayato wrote:
> PTAL

This looks right to me, though can I think we should put this in something like
tools/perf/experimental_benchmarks/ folder? 

Let me talk with the benchmarking group about this overall approach first before
we proceed further on code review.

[commit-bot: I haz the power, 2017-03-30 07:24:40]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2017-03-30 07:24:40]

Dry run: This issue passed the CQ dry run.

[hayato, 2017-03-30 07:41:22]

On 2017/03/30 at 07:06:15, nednguyen wrote:
> On 2017/03/30 05:56:56, hayato wrote:
> > PTAL
> 
> This looks right to me, though can I think we should put this in something
like tools/perf/experimental_benchmarks/ folder? 
> 
> Let me talk with the benchmarking group about this overall approach first
before we proceed further on code review.

Thanks. I am totally okay to put it in experimental-ish folder. That sounds good
for both; core maintainer(?) of infrastructures and users who want to take
advantage of benchmarks infra casually.

[hayato, 2017-04-05 03:33:00]

nedguyen@, it looks that the idea of using experimental folder is getting
approved in the benchmarking group.
Thank you for making it happen.

Should I wait for someone creating an experimental folder?

[nednguyen, 2017-04-06 15:44:50]

On 2017/04/05 03:33:00, hayato wrote:
> nedguyen@, it looks that the idea of using experimental folder is getting
> approved in the benchmarking group.
> Thank you for making it happen.
> 
> Should I wait for someone creating an experimental folder?

Sorry for the delay, I filed crbug.com/709063 about this. I will try to find
someone on my team to take over it, but you are also more than welcomed to take
it :-)

[hayato, 2017-04-07 04:03:20]

Thanks. This is not an urgent request because I think I am the only user of this
benchmark, at least for a month, or a quarter.
You don't need to think this as a high priority task. :)

[nednguyen, 2017-05-17 13:47:30]

On 2017/04/07 04:03:20, hayato wrote:
> Thanks. This is not an urgent request because I think I am the only user of
this
> benchmark, at least for a month, or a quarter.
> You don't need to think this as a high priority task. :)

Sorry for the delay. tools/perf/contrib is landed. You can land you web
component tests there. 

Also loading.desktop benchmark is landed. You can also consider adding your test
cases to
https://cs.chromium.org/chromium/src/tools/perf/page_sets/loading_desktop.py?...

However, because we are trying to keep the cycle time of tests small, you may
want to sync with Kouhei & Ksakamoto on how to keep the test time budget
unchanged with your new stories (maybe punting some of the old stories)

[hayato, 2017-05-18 01:32:59]

On 2017/05/17 at 13:47:30, nednguyen wrote:
> On 2017/04/07 04:03:20, hayato wrote:
> > Thanks. This is not an urgent request because I think I am the only user of
this
> > benchmark, at least for a month, or a quarter.
> > You don't need to think this as a high priority task. :)
> 
> Sorry for the delay. tools/perf/contrib is landed. You can land you web
component tests there. 
> 
> Also loading.desktop benchmark is landed. You can also consider adding your
test cases to
https://cs.chromium.org/chromium/src/tools/perf/page_sets/loading_desktop.py?...
> 
> However, because we are trying to keep the cycle time of tests small, you may
want to sync with Kouhei & Ksakamoto on how to keep the test time budget
unchanged with your new stories (maybe punting some of the old stories)

No problem. Thank you for your work!
Let me check what has changed, and consult kouhei@ and ksakamoto@ if necessary,
as you recommended.

I am afraid that I won't resume this task soon because I am now working on other
task. Let me ping you again when the CL is ready to be reviewed.