cc: Reland "Add UMA stats for record and raster time."

cc: Reland "Add UMA stats for record and raster time."

These should provide a basic smoke test for real-world regressions from
Slimming Paint phase 1.

BUG=471873, 486214
CQ_INCLUDE_TRYBOTS=tryserver.blink:linux_blink_rel

Committed: https://crrev.com/7b5b0557e0a757e040f8769857e7d78c6f0ed8c5
Cr-Commit-Position: refs/heads/master@{#331737}

[jbroman, 2015-05-14 03:47:37]

Patchset #2 (id:20001) has been deleted

[jbroman, 2015-05-14 03:47:46]

Patchset #2 (id:40001) has been deleted

[jbroman, 2015-05-14 03:50:05]

jbroman@chromium.org changed reviewers:
+ enne@chromium.org

[jbroman, 2015-05-14 03:50:05]

WDYT? I had to revert the previous patch because somehow this is evaluating to
NaN (and thus causing CHECK failure in saturated_cast).

I'm not happy not knowing how this is happening, but the branch is
today/tomorrow...

[jbroman, 2015-05-26 15:14:40]

On 2015/05/14 03:50:05, jbroman wrote:
> WDYT? I had to revert the previous patch because somehow this is evaluating to
> NaN (and thus causing CHECK failure in saturated_cast).
> 
> I'm not happy not knowing how this is happening, but the branch is
> today/tomorrow...

<< bump >>

[jbroman, 2015-05-27 18:38:04]

On 2015/05/26 15:14:40, jbroman wrote:
> On 2015/05/14 03:50:05, jbroman wrote:
> > WDYT? I had to revert the previous patch because somehow this is evaluating
to
> > NaN (and thus causing CHECK failure in saturated_cast).
> > 
> > I'm not happy not knowing how this is happening, but the branch is
> > today/tomorrow...
> 
> << bump >>

Bump again. I'm not super thrilled with this way of addressing 486214, but I've
failed to figure out how it happened and so this is a workaround. :/

[enne (OOO), 2015-05-27 18:56:11]

lgtm

Maybe put a comment by the nan that it's not clear why this is happening, but it
has crashed some small number of times?

[jbroman, 2015-05-27 19:00:57]

On 2015/05/27 18:56:11, enne wrote:
> lgtm
> 
> Maybe put a comment by the nan that it's not clear why this is happening, but
it
> has crashed some small number of times?

Done.

[jbroman, 2015-05-27 19:01:00]

The CQ bit was checked by jbroman@chromium.org

[jbroman, 2015-05-27 19:01:01]

The patchset sent to the CQ was uploaded after l-g-t-m from enne@chromium.org
Link to the patchset: https://codereview.chromium.org/1139743004/#ps80001
(title: "comment")

[commit-bot: I haz the power, 2015-05-27 19:04:23]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1139743004/80001

[commit-bot: I haz the power, 2015-05-27 19:11:30]

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

[commit-bot: I haz the power, 2015-05-27 19:11:31]

Try jobs failed on following builders:
  linux_chromium_compile_dbg_32_ng on tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/linux_chromium_...)
  ios_dbg_simulator_ninja on tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/ios_dbg_simulator...)
  ios_rel_device_ninja on tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/ios_rel_device_ni...)
  mac_chromium_compile_dbg_ng on tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_comp...)
  mac_chromium_rel_ng on tryserver.chromium.mac (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_rel_...)

[jbroman, 2015-05-27 19:17:25]

The CQ bit was checked by jbroman@chromium.org

[jbroman, 2015-05-27 19:17:26]

The patchset sent to the CQ was uploaded after l-g-t-m from enne@chromium.org
Link to the patchset: https://codereview.chromium.org/1139743004/#ps100001
(title: "merge with master (conflicts with cc/resources move)")

[commit-bot: I haz the power, 2015-05-27 19:19:09]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1139743004/100001

[commit-bot: I haz the power, 2015-05-27 19:29:27]

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

[commit-bot: I haz the power, 2015-05-27 19:29:28]

Try jobs failed on following builders:
  chromium_presubmit on tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/chromium_presub...)

[jbroman, 2015-05-27 19:32:56]

jbroman@chromium.org changed reviewers:
+ isherman@chromium.org

[jbroman, 2015-05-27 19:32:58]

isherman: Mind stamping for histograms?

These histograms haven't changed substantially since originally landed
(https://codereview.chromium.org/1075523002).

[jamesr, 2015-05-27 19:34:17]

jamesr@chromium.org changed reviewers:
+ jamesr@chromium.org

[jamesr, 2015-05-27 19:34:19]

https://codereview.chromium.org/1139743004/diff/100001/cc/base/histograms.cc
File cc/base/histograms.cc (right):

https://codereview.chromium.org/1139743004/diff/100001/cc/base/histograms.cc#...
cc/base/histograms.cc:42: // saturated_cast. http://crbug.com/486214
FYI in the past we've gotten unexpected results from floating point operations
on windows because some applications change the floating point control word (for
some threads): https://msdn.microsoft.com/en-us/library/e9b52ceh.aspx.  I think
norton (or one of the other bigger AVs) was doing this to Chrome in the past.
bug 486214 looks like it's not on windows but maybe somebody is mucking with the
floating point mode there.

[Ilya Sherman, 2015-05-27 20:56:53]

histograms lgtm

[jbroman, 2015-05-28 03:23:44]

The CQ bit was checked by jbroman@chromium.org

[commit-bot: I haz the power, 2015-05-28 03:24:03]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1139743004/100001

[commit-bot: I haz the power, 2015-05-28 03:37:10]

Committed patchset #4 (id:100001)

[commit-bot: I haz the power, 2015-05-28 03:37:57]

Patchset 4 (id:??) landed as
https://crrev.com/7b5b0557e0a757e040f8769857e7d78c6f0ed8c5
Cr-Commit-Position: refs/heads/master@{#331737}