tools/metrics/histograms/histograms.xml - Issue 864943002: Replaces instances of the deprecated TimeTicks::HighResNow() with TimeTicks::Now().

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Unified Diff: tools/metrics/histograms/histograms.xml

Issue 864943002: Replaces instances of the deprecated TimeTicks::HighResNow() with TimeTicks::Now(). (Closed) Base URL: https://chromium.googlesource.com/chromium/src.git@master

Patch Set: More changes based on review comments. Created 5 years, 11 months ago

Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.

Jump to:

Download patch

Index: tools/metrics/histograms/histograms.xml

diff --git a/tools/metrics/histograms/histograms.xml b/tools/metrics/histograms/histograms.xml

index 0b99c76701db51525e78c070d95e2d340da3e9f1..052eb0d549c51f226ad4a252ab3e061e3bc075bb 100644

--- a/tools/metrics/histograms/histograms.xml

+++ b/tools/metrics/histograms/histograms.xml

@@ -7183,9 +7183,8 @@ Therefore, the affected-histogram name has to have at least one dot in it.

Time between input event creation and the renderer receiving and starting to

process the event. For touch events on Windows, we measure from when the

event reaches Chrome, whereas on other platforms we use the timestamp from

- the kernel. On Windows, this metric is only reported when

- |IsHighResNowFastAndReliable| is true, which will introduce some sampling

- bias.

+ the kernel. On Windows, this metric is only reported when |IsHighResolution|

+ is true, which will introduce some sampling bias.

</summary>

</histogram>

@@ -7196,8 +7195,7 @@ Therefore, the affected-histogram name has to have at least one dot in it.

starting to process the event. For touch events on Windows, we measure from

when the event reaches Chrome, whereas on other platforms we use the

timestamp from the kernel. On Windows, this metric is only reported when

- |IsHighResNowFastAndReliable| is true, which will introduce some sampling

- bias.

+ |IsHighResolution| is true, which will introduce some sampling bias.

</summary>

</histogram>

@@ -7220,8 +7218,8 @@ Therefore, the affected-histogram name has to have at least one dot in it.

reaches the Impl thread. Maximum is 1000ms. On Windows, we measure from when

the touch event reaches Chrome, whereas on other platforms we use the

timestamp from the kernel. On Windows, this metric is only reported when

- |IsHighResNowFastAndReliable| is true, which will introduce some sampling

- bias. This supersedes the Event.Latency.RendererImpl.GestureScroll metric.

+ |IsHighResolution| is true, which will introduce some sampling bias. This

+ supersedes the Event.Latency.RendererImpl.GestureScroll metric.

</summary>

</histogram>

« no previous file with comments | « tools/gn/trace.cc ('k') | tools/valgrind/gtest_exclude/base_unittests.gtest_win32.txt » ('j') | no next file with comments »