[Bindings][UMA] Split user metrics for window proxy initialization

Split user metrics for window proxy initialization.

Currently we have two UMA to measure time spent in window proxies initialization
- Blink.Binding.InitializeMainWindowProxy
- Blink.Binding.InitializeNonMainWindowProxy
but now WindowProxy was split into LocalWP and RemoteWP.
https://chromium.googlesource.com/chromium/src/+/690c3cf203b94623e5adbece7d6b4afc3501cd94

So I would like to split those UMAs to track performance more precisely.
- Blink.Binding.InitializeMainLocalWindowProxy
- Blink.Binding.InitializeMainRemoteWindowProxy
- Blink.Binding.InitializeNonMainLocalWindowProxy
- Blink.Binding.InitializeNonMainRemoteWindowProxy


BUG=588893
Review-Url: https://codereview.chromium.org/2771723005
Cr-Commit-Position: refs/heads/master@{#459705}
Committed: https://chromium.googlesource.com/chromium/src/+/dd92156efac57169b45aeb0094111b8d94302b12

[peria, 2017-03-24 06:16:32]

Description was changed from

==========
Split UMAs for window proxy initialization

BUG=588893
==========

to

==========
Split user metrics for window proxy initialization.

Currently we have two UMA to measure time spent in window proxies initialization
- Blink.Binding.InitializeMainWindowProxy
- Blink.Binding.InitializeNonMainWindowProxy
but now WindowProxy was split into LocalWP and RemoteWP, and their
initialization phase are different.
https://chromium.googlesource.com/chromium/src/+/690c3cf203b94623e5adbece7d6b...

So I would like to split UMA too, to track performance more precisely.


BUG=588893
==========

[peria, 2017-03-24 07:20:11]

Patchset #1 (id:1) has been deleted

[peria, 2017-03-24 07:20:23]

Patchset #1 (id:20001) has been deleted

[peria, 2017-03-24 07:20:33]

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

[commit-bot: I haz the power, 2017-03-24 07:20:48]

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-03-24 07:29:08]

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

[commit-bot: I haz the power, 2017-03-24 07:29:09]

Dry run: Try jobs failed on following builders:
  cast_shell_android on master.tryserver.chromium.android (JOB_FAILED,
https://build.chromium.org/p/tryserver.chromium.android/builders/cast_shell_a...)

[peria, 2017-03-24 08:03:44]

Patchset #1 (id:40001) has been deleted

[peria, 2017-03-24 08:07:27]

Description was changed from

==========
Split user metrics for window proxy initialization.

Currently we have two UMA to measure time spent in window proxies initialization
- Blink.Binding.InitializeMainWindowProxy
- Blink.Binding.InitializeNonMainWindowProxy
but now WindowProxy was split into LocalWP and RemoteWP, and their
initialization phase are different.
https://chromium.googlesource.com/chromium/src/+/690c3cf203b94623e5adbece7d6b...

So I would like to split UMA too, to track performance more precisely.


BUG=588893
==========

to

==========
Split user metrics for window proxy initialization.

Currently we have two UMA to measure time spent in window proxies initialization
- Blink.Binding.InitializeMainWindowProxy
- Blink.Binding.InitializeNonMainWindowProxy
but now WindowProxy was split into LocalWP and RemoteWP, and RemoteWP works
only for non main frames.
https://chromium.googlesource.com/chromium/src/+/690c3cf203b94623e5adbece7d6b...

So I would like to split NonMainWindowProxy to track performance more precisely.
- Blink.Binding.InitializeMainWindowProxy
- Blink.Binding.InitializeNonMainLocalWindowProxy
- Blink.Binding.InitializeNonMainRemoteWindowProxy

BUG=588893
==========

[peria, 2017-03-24 08:08:08]

Description was changed from

==========
Split user metrics for window proxy initialization.

Currently we have two UMA to measure time spent in window proxies initialization
- Blink.Binding.InitializeMainWindowProxy
- Blink.Binding.InitializeNonMainWindowProxy
but now WindowProxy was split into LocalWP and RemoteWP, and RemoteWP works
only for non main frames.
https://chromium.googlesource.com/chromium/src/+/690c3cf203b94623e5adbece7d6b...

So I would like to split NonMainWindowProxy to track performance more precisely.
- Blink.Binding.InitializeMainWindowProxy
- Blink.Binding.InitializeNonMainLocalWindowProxy
- Blink.Binding.InitializeNonMainRemoteWindowProxy

BUG=588893
==========

to

==========
Split user metrics for window proxy initialization.

Currently we have two UMA to measure time spent in window proxies initialization
- Blink.Binding.InitializeMainWindowProxy
- Blink.Binding.InitializeNonMainWindowProxy
but now WindowProxy was split into LocalWP and RemoteWP, and RemoteWP works
only for non main frames.
https://chromium.googlesource.com/chromium/src/+/690c3cf203b94623e5adbece7d6b...

So I would like to split NonMainWindowProxy to track performance more precisely.
- Blink.Binding.InitializeMainWindowProxy  (as-is)
- Blink.Binding.InitializeNonMainLocalWindowProxy
- Blink.Binding.InitializeNonMainRemoteWindowProxy

BUG=588893
==========

[peria, 2017-03-24 08:10:31]

peria@chromium.org changed reviewers:
+ dcheng@chromium.org, haraken@chromium.org, yukishiino@chromium.org

[peria, 2017-03-24 08:10:32]

PTL

[peria, 2017-03-24 08:12:29]

On 2017/03/24 08:10:32, peria (slow this week) wrote:
> PTL

I'll add an OWNER of histograms.xml after your reviews.

[dcheng, 2017-03-24 08:20:54]

On 2017/03/24 08:12:29, peria (slow this week) wrote:
> On 2017/03/24 08:10:32, peria (slow this week) wrote:
> > PTL
> 
> I'll add an OWNER of histograms.xml after your reviews.

Per the other CL, we can have remote window proxies for the main frame. Though
I'm not sure we actually need to distinguish between main frame and non main
frame time for remote window proxy, it can't hurt.

(Sorry for missing this in my CL: it was in my to-do list to split this uma, but
then I missed it)

[peria, 2017-03-24 08:37:12]

On 2017/03/24 08:20:54, dcheng wrote:
> On 2017/03/24 08:12:29, peria (slow this week) wrote:
> > On 2017/03/24 08:10:32, peria (slow this week) wrote:
> > > PTL
> > 
> > I'll add an OWNER of histograms.xml after your reviews.
> 
> Per the other CL, we can have remote window proxies for the main frame. Though
> I'm not sure we actually need to distinguish between main frame and non main
> frame time for remote window proxy, it can't hurt.
> 
> (Sorry for missing this in my CL: it was in my to-do list to split this uma,
but
> then I missed it)

No problem ;)

Then, I'll simply split each original metric into 2.
(mainWP --> mainLocalWP + mainRemoteWP,
 nonMainWP --> nonMainLocalWP + nonMainRemoteWP)
We can obsolete or just ignore some results, if we don't need them.

[peria, 2017-03-24 09:29:43]

PTAL

[Yuki, 2017-03-24 10:21:50]

Defer to dcheng@.  LGTM on my side.

[haraken, 2017-03-24 10:23:38]

LGTM

(You need to ask review for histograms.)

[dcheng, 2017-03-27 02:44:50]

LGTM

[peria, 2017-03-27 03:37:31]

Description was changed from

==========
Split user metrics for window proxy initialization.

Currently we have two UMA to measure time spent in window proxies initialization
- Blink.Binding.InitializeMainWindowProxy
- Blink.Binding.InitializeNonMainWindowProxy
but now WindowProxy was split into LocalWP and RemoteWP, and RemoteWP works
only for non main frames.
https://chromium.googlesource.com/chromium/src/+/690c3cf203b94623e5adbece7d6b...

So I would like to split NonMainWindowProxy to track performance more precisely.
- Blink.Binding.InitializeMainWindowProxy  (as-is)
- Blink.Binding.InitializeNonMainLocalWindowProxy
- Blink.Binding.InitializeNonMainRemoteWindowProxy

BUG=588893
==========

to

==========
Split user metrics for window proxy initialization.

Currently we have two UMA to measure time spent in window proxies initialization
- Blink.Binding.InitializeMainWindowProxy
- Blink.Binding.InitializeNonMainWindowProxy
but now WindowProxy was split into LocalWP and RemoteWP, and RemoteWP works
only for non main frames.
https://chromium.googlesource.com/chromium/src/+/690c3cf203b94623e5adbece7d6b...

So I would like to split NonMainWindowProxy to track performance more precisely.
- Blink.Binding.InitializeMainLocalWindowProxy
- Blink.Binding.InitializeMainRemoteWindowProxy
- Blink.Binding.InitializeNonMainLocalWindowProxy
- Blink.Binding.InitializeNonMainRemoteWindowProxy

BUG=588893
==========

[peria, 2017-03-27 03:38:25]

Description was changed from

==========
Split user metrics for window proxy initialization.

Currently we have two UMA to measure time spent in window proxies initialization
- Blink.Binding.InitializeMainWindowProxy
- Blink.Binding.InitializeNonMainWindowProxy
but now WindowProxy was split into LocalWP and RemoteWP, and RemoteWP works
only for non main frames.
https://chromium.googlesource.com/chromium/src/+/690c3cf203b94623e5adbece7d6b...

So I would like to split NonMainWindowProxy to track performance more precisely.
- Blink.Binding.InitializeMainLocalWindowProxy
- Blink.Binding.InitializeMainRemoteWindowProxy
- Blink.Binding.InitializeNonMainLocalWindowProxy
- Blink.Binding.InitializeNonMainRemoteWindowProxy

BUG=588893
==========

to

==========
Split user metrics for window proxy initialization.

Currently we have two UMA to measure time spent in window proxies initialization
- Blink.Binding.InitializeMainWindowProxy
- Blink.Binding.InitializeNonMainWindowProxy
but now WindowProxy was split into LocalWP and RemoteWP.
https://chromium.googlesource.com/chromium/src/+/690c3cf203b94623e5adbece7d6b...

So I would like to split those UMAs to track performance more precisely.
- Blink.Binding.InitializeMainLocalWindowProxy
- Blink.Binding.InitializeMainRemoteWindowProxy
- Blink.Binding.InitializeNonMainLocalWindowProxy
- Blink.Binding.InitializeNonMainRemoteWindowProxy


BUG=588893
==========

[peria, 2017-03-27 03:43:47]

The CQ bit was checked by peria@chromium.org

[commit-bot: I haz the power, 2017-03-27 03:44:17]

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-03-27 05:11:57]

CQ is committing da patch.

Bot data: {"patchset_id": 80001, "attempt_start_ts": 1490586227863560,
"parent_rev": "9e4242231a21fb5ebdc990ad3cbc50b9afdf00d3", "commit_rev":
"dd92156efac57169b45aeb0094111b8d94302b12"}

[commit-bot: I haz the power, 2017-03-27 05:13:14]

Description was changed from

==========
Split user metrics for window proxy initialization.

Currently we have two UMA to measure time spent in window proxies initialization
- Blink.Binding.InitializeMainWindowProxy
- Blink.Binding.InitializeNonMainWindowProxy
but now WindowProxy was split into LocalWP and RemoteWP.
https://chromium.googlesource.com/chromium/src/+/690c3cf203b94623e5adbece7d6b...

So I would like to split those UMAs to track performance more precisely.
- Blink.Binding.InitializeMainLocalWindowProxy
- Blink.Binding.InitializeMainRemoteWindowProxy
- Blink.Binding.InitializeNonMainLocalWindowProxy
- Blink.Binding.InitializeNonMainRemoteWindowProxy


BUG=588893
==========

to

==========
Split user metrics for window proxy initialization.

Currently we have two UMA to measure time spent in window proxies initialization
- Blink.Binding.InitializeMainWindowProxy
- Blink.Binding.InitializeNonMainWindowProxy
but now WindowProxy was split into LocalWP and RemoteWP.
https://chromium.googlesource.com/chromium/src/+/690c3cf203b94623e5adbece7d6b...

So I would like to split those UMAs to track performance more precisely.
- Blink.Binding.InitializeMainLocalWindowProxy
- Blink.Binding.InitializeMainRemoteWindowProxy
- Blink.Binding.InitializeNonMainLocalWindowProxy
- Blink.Binding.InitializeNonMainRemoteWindowProxy


BUG=588893

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

[commit-bot: I haz the power, 2017-03-27 05:13:16]

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