Add several tough paint performance tests

Add several tough paint performance tests

These tests are based on the test cases in the bug reports to demostrate
slow compositing, paint invalidation and perhaps also painting.

BUG=646719, 665223, 692614
Review-Url: https://codereview.chromium.org/2723243002
Cr-Commit-Position: refs/heads/master@{#454152}
Committed: https://chromium.googlesource.com/chromium/src/+/fd7fc207884807c1b5365c191cf6d5cb55e33f4c

[Xianzhu, 2017-03-01 19:33:56]

wangxianzhu@chromium.org changed reviewers:
+ chrishtr@chromium.org, pdr@chromium.org

[Xianzhu, 2017-03-01 19:33:56]

Besides the files shown in this CL, there are also other files added in this CL
but not shown because they are too big:

- ecma-262-fast-scroll.html (saved from https://bterlson.github.io/ecma262/)

- ecma-262-slow-scroll.html (with forced slow scrolling with the following
style: #spec-container { will-change: auto; })

- github-huge-body-scroll.html (saved from
https://github.com/mdittmer/web-apis/blob/fd8ba1f1a491897025b7bd78bd887c9bec3...)

They are added the following code to measure performance:

ecma-262-fast-scroll.html and ecma-262-slow-scroll.html:
<script src="../resources/runner.js"></script>
<script>
onload = function() {
  PerfTestRunner.measureFrameTime({
    run: function() {
      document.getElementById('spec-container').scrollTop += 20;
    },
  });
};
</script>


github-huge-body-scroll.html:
<script src="../resources/runner.js"></script>
<script>
onload = function() {
  window.scrollTo(0, 0);
  PerfTestRunner.measureFrameTime({
    run: function() {
      window.scrollBy(0, 20);
    },
  });
};
</script>

[chrishtr, 2017-03-01 21:23:11]

How big are the files?

I wonder if there is a way to extract their purpose without adding them
explicitly to the
repo. Is it just lots and lots of text in a scrolling div?

[Xianzhu, 2017-03-01 21:55:21]

On 2017/03/01 21:23:11, chrishtr wrote:
> How big are the files?
> 
> I wonder if there is a way to extract their purpose without adding them
> explicitly to the
> repo. Is it just lots and lots of text in a scrolling div?

Each of the 3 big files is about 5~6MB. Will try to create smaller tests for the
purposes of the big ones.

[Xianzhu, 2017-03-02 00:51:21]

Description was changed from

==========
Add several tough paint performance tests

These tests are from bug reports to demostrate slow paint invalidation
and perhaps also painting.

BUG=646719,665223,692614
==========

to

==========
Add several tough paint performance tests

These tests are based on the test cases in the bug reports to demostrate
slow compositing, paint invalidation and perhaps also painting.

BUG=646719,665223,692614
==========

[Xianzhu, 2017-03-02 00:53:48]

On 2017/03/01 21:55:21, Xianzhu wrote:
> On 2017/03/01 21:23:11, chrishtr wrote:
> > How big are the files?
> > 
> > I wonder if there is a way to extract their purpose without adding them
> > explicitly to the
> > repo. Is it just lots and lots of text in a scrolling div?
> 
> Each of the 3 big files is about 5~6MB. Will try to create smaller tests for
the
> purposes of the big ones.

Done. Ptal.

[chrishtr, 2017-03-02 00:55:04]

lgtm

[chrishtr, 2017-03-02 00:55:07]

The CQ bit was checked by chrishtr@chromium.org

[commit-bot: I haz the power, 2017-03-02 00:55:43]

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

[pdr., 2017-03-02 01:09:06]

On 2017/03/02 at 00:55:43, commit-bot wrote:
> CQ is trying da patch. Follow status at
>  
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

LGTM 2

[commit-bot: I haz the power, 2017-03-02 02:13:35]

CQ is committing da patch.

Bot data: {"patchset_id": 10001, "attempt_start_ts": 1488416107798760,
"parent_rev": "4897208670d3d79eb2426e9d55b971103e87bdd7", "commit_rev":
"fd7fc207884807c1b5365c191cf6d5cb55e33f4c"}

[commit-bot: I haz the power, 2017-03-02 02:14:16]

Description was changed from

==========
Add several tough paint performance tests

These tests are based on the test cases in the bug reports to demostrate
slow compositing, paint invalidation and perhaps also painting.

BUG=646719,665223,692614
==========

to

==========
Add several tough paint performance tests

These tests are based on the test cases in the bug reports to demostrate
slow compositing, paint invalidation and perhaps also painting.

BUG=646719,665223,692614

Review-Url: https://codereview.chromium.org/2723243002
Cr-Commit-Position: refs/heads/master@{#454152}
Committed:
https://chromium.googlesource.com/chromium/src/+/fd7fc207884807c1b5365c191cf6...
==========

[commit-bot: I haz the power, 2017-03-02 02:14:17]

Committed patchset #2 (id:10001) as
https://chromium.googlesource.com/chromium/src/+/fd7fc207884807c1b5365c191cf6...