All graphs for this bug:
  https://chromeperf.appspot.com/group_report?bug_id=773020

(For debugging:) Original alerts at time of bug-filing:
  https://chromeperf.appspot.com/group_report?sid=f488c1810a2f455c0331647ebcd4bc4aeb89a24356c6a6d067f9d24ab7126288


Bot(s) for this bug's original alert(s):

chromium-rel-mac-retina
chromium-rel-mac11-air
chromium-rel-mac11-pro

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/14a4c4f1780000

😿 Pinpoint job stopped with an error.
https://pinpoint-dot-chromeperf.appspot.com/job/14a4c4f1780000

Filed a bug for the error.
https://github.com/catapult-project/catapult/issues/3957

The fix hasn't been reviewed yet. https://chromium-review.googlesource.com/c/catapult/+/707996
But I deployed a dev version with it in, and am re-kicking the job. Shhh, don't tell anyone.

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/12ceae29780000

😿 Pinpoint job stopped with an error.
https://pinpoint-dot-chromeperf.appspot.com/job/12ceae29780000

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/14fcf1f9780000

📍 Found a significant difference after 1 commit.
https://pinpoint-dot-chromeperf.appspot.com/job/14fcf1f9780000

Add scaling capability to CopyOutputRequests. (Part 2 of 2)
By miu@chromium.org · Fri Oct 06 23:50:16 2017
chromium @ 081f9dcc223a535202a52c351392514ad5635650

Understanding performance regressions:
  http://g.co/ChromePerformanceRegressions

Why was that issue not assigned to culprit CL owner?

Sorry, it's not implemented yet!
https://github.com/catapult-project/catapult/issues/3890

As mentioned in  bug 768335 , a lot of things are moving around right now; and when that's done, the performance issues may self-resolve. So, marking this bug as blocked on 754872.

Removing Performance-Sheriff label so we don't keep pinging, since there's a lot of active work going on in the blocking bug but it doesn't seem like having us pinging this one is helpful.

Obsolete.