E.g. https://cs.chromium.org/chromium/src/third_party/blink/perf_tests/shadow_dom/v1-large-shallow-layout.html
It adds elements in setup: and removes them in done: but setup is run before every iteration and done is only run at the end. So the DOM gets larger and larger with each iteration and the benchmark gets slower and slower. The resulting timings are monotonically increasing and the last one is about 2x the first time.
I've also found other perf_tests outside of shadow_dom that have the same problem although I haven't yet found any where it actually impacts the timing.
Comment 1 by bugdroid1@chromium.org
, Dec 21