DescriptionRevert Renderer.LayoutMs.
We created this histogram in the hope that some sort of useful pattern
might emerge. It turned out that there's a huge spike at 0 due to
incremental layouts, then it tapers off smoothly all the way through 1
minute, apparently an exponential distribution. The mean is about 1ms.
If performance optimizations improve benchmarked cases but regress
un-benchmarked cases, we would not be able to tell from these histograms
-- a fraction of samples would be smeared one way and another fraction
would be smeared the other way, likely resulting in no visible
difference. So this histogram is useless and a waste of space.
Instead of counting all layouts together, it might make more sense to
count specific kinds of layout separately, like a
micro-benchmark-in-the-wild. E.g. one histogram for when a layout
touches >100 floats/table cells/lots of complex text. If we identify
kinds of layout like that, then maybe we'll add new histograms here in
the hope that they would present a log-normal with a mean value that
could visibly move towards zero due to targetted performance
optimizations, or shrink as sites stop abusing layout.
No BUG, but these histograms were created in these CLs:
https://codereview.chromium.org/882293002
https://codereview.chromium.org/877293003
Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=191379
Patch Set 1 #
Messages
Total messages: 11 (3 generated)
|