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

Side by Side Diff: docs/how-to-write-metrics.md

Issue 2977283002: Ownership into GenericSets (Closed)
Patch Set: Fix reserved info reference Created 3 years, 5 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:
View unified diff | Download patch
OLDNEW
1 <!-- Copyright 2016 The Chromium Authors. All rights reserved. 1 <!-- Copyright 2016 The Chromium Authors. All rights reserved.
2 Use of this source code is governed by a BSD-style license that can be 2 Use of this source code is governed by a BSD-style license that can be
3 found in the LICENSE file. 3 found in the LICENSE file.
4 --> 4 -->
5 5
6 # How to Write Metrics 6 # How to Write Metrics
7 7
8 Timeline-Based Measurement v2 is a system for computing metrics from traces. 8 Timeline-Based Measurement v2 is a system for computing metrics from traces.
9 9
10 A TBM2 metric is a Javascript function that takes a trace Model and produces 10 A TBM2 metric is a Javascript function that takes a trace Model and produces
(...skipping 197 matching lines...) Expand 10 before | Expand all | Expand 10 after
208 ![](/docs/images/how-to-write-metrics-revision.png) 208 ![](/docs/images/how-to-write-metrics-revision.png)
209 209
210 * [BuildbotInfo](/tracing/tracing/value/diagnostics/buildbot_info.html): 210 * [BuildbotInfo](/tracing/tracing/value/diagnostics/buildbot_info.html):
211 This is automatically attached to every Histogram produced by Chrome's 211 This is automatically attached to every Histogram produced by Chrome's
212 performance testing buildbots. Structurally, it's a class with explicit named 212 performance testing buildbots. Structurally, it's a class with explicit named
213 fields. Conceptually, it contains information about the buildbot process that 213 fields. Conceptually, it contains information about the buildbot process that
214 ran telemetry. Visually, it is displayed as a table. 214 ran telemetry. Visually, it is displayed as a table.
215 215
216 ![](/docs/images/how-to-write-metrics-buildbot.png) 216 ![](/docs/images/how-to-write-metrics-buildbot.png)
217 217
218 * [Ownership](/tracing/tracing/value/diagnostics/ownership.html):
219 This is automatically attached to every Histogram produced by Temeletry.
220 Structurally, it's a class with explicit named fields. Conceptually, it
221 contains information about the owners of benchmarks run by Telemetry, such
222 as the owners' emails addresses and Monorail component.
223
224 ### Other Diagnostics 218 ### Other Diagnostics
225 219
226 * [Scalar](/tracing/tracing/value/diagnostics/scalar.html): 220 * [Scalar](/tracing/tracing/value/diagnostics/scalar.html):
227 Metrics must not use this, since it is incapable of being merged. It is 221 Metrics must not use this, since it is incapable of being merged. It is
228 mentioned here for completeness. It wraps a Scalar, which is just a 222 mentioned here for completeness. It wraps a Scalar, which is just a
229 unitted number. This is only to allow Histograms in other parts of the trace 223 unitted number. This is only to allow Histograms in other parts of the trace
230 viewer to display number sample diagnostics more intelligently than 224 viewer to display number sample diagnostics more intelligently than
231 GenericSet can. If a metric wants to display number sample diagnostics 225 GenericSet can. If a metric wants to display number sample diagnostics
232 intelligently, then it should use RelatedHistogramSet or RelatedHistogramMap; 226 intelligently, then it should use RelatedHistogramSet or RelatedHistogramMap;
233 if it does not want to monitor changes in those numbers, then the TBM2 227 if it does not want to monitor changes in those numbers, then the TBM2
(...skipping 46 matching lines...) Expand 10 before | Expand all | Expand 10 after
280 * Instead of having one category for all story grouping keys, each grouping 274 * Instead of having one category for all story grouping keys, each grouping
281 individual grouping key may be listed as a category. For example, in Page 275 individual grouping key may be listed as a category. For example, in Page
282 Cycler v2 benchmarks, the "cache_temperature" grouping key would be 276 Cycler v2 benchmarks, the "cache_temperature" grouping key would be
283 displayed as a category. 277 displayed as a category.
284 * Choosing groups builds a hierarchy of histograms that is filled in by merging 278 * Choosing groups builds a hierarchy of histograms that is filled in by merging
285 histograms from the bottom up. Expanding the rows of histogram-set-table, any 279 histograms from the bottom up. Expanding the rows of histogram-set-table, any
286 leaf nodes are histograms that were loaded, and their ancestors are computed b y 280 leaf nodes are histograms that were loaded, and their ancestors are computed b y
287 merging. 281 merging.
288 * histogram-set-table uses the "label" property of TelemetryInfo to define the 282 * histogram-set-table uses the "label" property of TelemetryInfo to define the
289 columns of the table. 283 columns of the table.
OLDNEW

Powered by Google App Engine
This is Rietveld 408576698