Commit f0312e9d authored by Mark Pearson's avatar Mark Pearson Committed by Commit Bot

Histograms README - fix broken link

TBR=isherman

Change-Id: Ie1a9cb60a136b93c9f22c67fec8d538c69962b91
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/1827676
Commit-Queue: Mark Pearson <mpearson@chromium.org>
Reviewed-by: default avatarMark Pearson <mpearson@chromium.org>
Cr-Commit-Position: refs/heads/master@{#700361}
parent ac2541e7
...@@ -240,9 +240,9 @@ for larger numbers. The macros default to 50 buckets (or 100 buckets for ...@@ -240,9 +240,9 @@ for larger numbers. The macros default to 50 buckets (or 100 buckets for
histograms with wide ranges) which is appropriate for most purposes. Because histograms with wide ranges) which is appropriate for most purposes. Because
histograms pre-allocate all the buckets, the number of buckets selected histograms pre-allocate all the buckets, the number of buckets selected
directly dictate how much memory is used. Do not exceed 100 buckets without directly dictate how much memory is used. Do not exceed 100 buckets without
good reason (and consider whether [sparse histograms](#When-To-Use-Sparse- good reason (and consider whether [sparse
Histograms) might work better for you in that case--they do not pre- allocate histograms](#When-To-Use-Sparse-Histograms) might work better for you in that
their buckets). case--they do not pre-allocate their buckets).
### Timing Histograms ### Timing Histograms
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment