Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(10)

Issues Search
    My Issues | Starred     Open | Closed | All

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

Side-by-side diff isn't available for this file because of its large size.
Issue 1407093003: Add start/finish navigation to startup metrics. (Closed) Base URL: https://chromium.googlesource.com/chromium/src.git@a2_better_ownership_model_firstwebcontentsprofiler
Patch Set: merge NavigationEntryCommitted() logic into DidFinishNavigation() Created 5 years, 1 month 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
« no previous file with comments | « components/startup_metric_utils/startup_metric_utils.cc ('k') | no next file » | no next file with comments »
Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
Index: tools/metrics/histograms/histograms.xml
diff --git a/tools/metrics/histograms/histograms.xml b/tools/metrics/histograms/histograms.xml
index 92a6187c32c9641d91add5b4543c623220a552ae..e0900d8a42138f6c55ad9284792d44e40aeec6ab 100644
--- a/tools/metrics/histograms/histograms.xml
+++ b/tools/metrics/histograms/histograms.xml
@@ -44136,9 +44136,9 @@ http://cs/file:chrome/histograms.xml - but prefer this file for new entries.
<histogram name="Startup.FirstCommitNavigationTime" units="milliseconds">
<owner>pasko@chromium.org</owner>
<summary>
- The time from the earliest entry point in the browser process to the moment
- the first navigation is committed, i.e. when renderer gets the first byte of
- the document.
+ [Android only] The time from the earliest entry point in the browser process
+ to the moment the first navigation is committed, i.e. when renderer gets the
+ first byte of the document.
</summary>
</histogram>
@@ -44146,34 +44146,55 @@ http://cs/file:chrome/histograms.xml - but prefer this file for new entries.
enum="StartupProfilingFinishReason">
<owner>gab@chromium.org</owner>
<summary>
- The reason for which startup profiling was deemed complete. Logged once per
- session on startup.
+ [Desktop] The reason for which startup profiling was deemed complete. Logged
+ once per session on startup.
</summary>
</histogram>
<histogram name="Startup.FirstWebContents.MainFrameLoad" units="milliseconds">
<owner>erikchen@chromium.org</owner>
+ <owner>gab@chromium.org</owner>
<summary>
- Measure the elapsed time from process launch to the first main frame load of
- the first web contents.
+ [Desktop] Measure the elapsed time from process launch to the first main
+ frame load of the first web contents.
+ </summary>
+</histogram>
+
+<histogram name="Startup.FirstWebContents.MainNavigationFinished"
+ units="milliseconds">
+ <owner>gab@chromium.org</owner>
+ <summary>
+ [Desktop] Measure the elapsed time from process launch to the moment when
+ the navigation is committed (first bytes received) in the first web
+ contents' main frame.
+ </summary>
+</histogram>
+
+<histogram name="Startup.FirstWebContents.MainNavigationStart"
+ units="milliseconds">
+ <owner>gab@chromium.org</owner>
+ <summary>
+ [Desktop] Measure the elapsed time from process launch to the beginning of
+ navigation in the first web contents' main frame.
</summary>
</histogram>
<histogram name="Startup.FirstWebContents.NonEmptyPaint" units="milliseconds">
<owner>erikchen@chromium.org</owner>
+ <owner>gab@chromium.org</owner>
<summary>
- Measure the elapsed time from process launch to the first non-empty paint of
- the first web contents.
+ [Desktop] Measure the elapsed time from process launch to the first non-
+ empty paint of the first web contents.
</summary>
</histogram>
<histogram name="Startup.FirstWebContents.UINotResponsive" units="milliseconds">
<owner>gayane@chromium.org</owner>
<summary>
- Measures the execution time for a single task to execute on UI if it was not
- possible to execute UI tasks under 1/60s within certain limits, after
- WebContents was painted at least once. This is recorded at most once per
- Chrome launch. Used as a measure of responsiveness on startup.
+ [Desktop] Measures the execution time for a single task to execute on UI if
+ it was not possible to execute UI tasks under 1/60s within certain limits,
+ after WebContents was painted at least once. This is recorded at most once
+ per Chrome launch. Used as a measure of responsiveness on startup.
</summary>
</histogram>
@@ -44181,10 +44202,10 @@ http://cs/file:chrome/histograms.xml - but prefer this file for new entries.
units="milliseconds">
<owner>gayane@chromium.org</owner>
<summary>
- Measures the elapsed time for a single task to execute on UI if it was not
- possible to execute it under 1/60s within certain limits, 10 second after
- first WebContents was painted at least once. This is recorded at most once
- per Chrome launch. Used as a measure of responsiveness on startup.
+ [Desktop] Measures the elapsed time for a single task to execute on UI if it
+ was not possible to execute it under 1/60s within certain limits, 10 second
+ after first WebContents was painted at least once. This is recorded at most
+ once per Chrome launch. Used as a measure of responsiveness on startup.
</summary>
</histogram>
@@ -44192,19 +44213,20 @@ http://cs/file:chrome/histograms.xml - but prefer this file for new entries.
units="milliseconds">
<owner>gayane@chromium.org</owner>
<summary>
- Measures the elapsed time for a single task to execute on UI if it was not
- possible to execute it under 1/60s within certain limits, 1 second after
- first WebContents was painted at least once. This is recorded at most once
- per Chrome launch. Used as a measure of responsiveness on startup.
+ [Desktop] Measures the elapsed time for a single task to execute on UI if it
+ was not possible to execute it under 1/60s within certain limits, 1 second
+ after first WebContents was painted at least once. This is recorded at most
+ once per Chrome launch. Used as a measure of responsiveness on startup.
</summary>
</histogram>
<histogram name="Startup.FirstWebContents.UIResponsive" units="milliseconds">
<owner>gayane@chromium.org</owner>
<summary>
- Measures the elapsed time it takes for a task to execute on UI under 1/60s
- after first WebContents was painted at least once. This is recorded at most
- once per Chrome launch. Used as a measure of responsiveness on startup.
+ [Desktop] Measures the elapsed time it takes for a task to execute on UI
+ under 1/60s after first WebContents was painted at least once. This is
+ recorded at most once per Chrome launch. Used as a measure of responsiveness
+ on startup.
</summary>
</histogram>
@@ -44212,9 +44234,10 @@ http://cs/file:chrome/histograms.xml - but prefer this file for new entries.
units="milliseconds">
<owner>gayane@chromium.org</owner>
<summary>
- Measures the elapsed time it takes for a task to execute on UI under 1/60s,
- 10 second after the first WebContents was painted. This is recorded at most
- once per Chrome launch. Used as a measure of responsiveness on startup.
+ [Desktop] Measures the elapsed time it takes for a task to execute on UI
+ under 1/60s, 10 second after the first WebContents was painted. This is
+ recorded at most once per Chrome launch. Used as a measure of responsiveness
+ on startup.
</summary>
</histogram>
@@ -44222,9 +44245,10 @@ http://cs/file:chrome/histograms.xml - but prefer this file for new entries.
units="milliseconds">
<owner>gayane@chromium.org</owner>
<summary>
- Measures the elapsed time it takes for a task to execute on UI under 1/60s,
- 1 second after the first WebContents was painted. This is recorded at most
- once per Chrome launch. Used as a measure of responsiveness on startup.
+ [Desktop] Measures the elapsed time it takes for a task to execute on UI
+ under 1/60s, 1 second after the first WebContents was painted. This is
+ recorded at most once per Chrome launch. Used as a measure of responsiveness
+ on startup.
</summary>
</histogram>
@@ -72890,6 +72914,9 @@ To add a new entry, add it with any value and run test to compute valid value.
<int value="3" label="Abandoned because profiled content was destroyed"/>
<int value="4"
label="Abandoned because profiled content was navigated away from"/>
+ <int value="5"
+ label="Abandoned because profiled content failed to load its main
+ resource"/>
</enum>
<enum name="StartupTemperature" type="int">
@@ -79913,6 +79940,8 @@ To add a new entry, add it with any value and run test to compute valid value.
<affected-histogram name="Startup.BrowserOpenTabs"/>
<affected-histogram name="Startup.BrowserWindowDisplay"/>
<affected-histogram name="Startup.FirstWebContents.MainFrameLoad"/>
+ <affected-histogram name="Startup.FirstWebContents.MainNavigationFinished"/>
+ <affected-histogram name="Startup.FirstWebContents.MainNavigationStart"/>
<affected-histogram name="Startup.FirstWebContents.NonEmptyPaint"/>
<affected-histogram name="Startup.LoadTime.ExeMainToDllMain"/>
<affected-histogram name="Startup.LoadTime.ProcessCreateToDllMain"/>
« no previous file with comments | « components/startup_metric_utils/startup_metric_utils.cc ('k') | no next file » | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698