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

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


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

Android Nexus5 Perf

rendering.mobile - Benchmark documentation link:
  https://bit.ly/rendering-benchmarks

📍 Pinpoint job started.
https://pinpoint-dot-chromeperf.appspot.com/job/113485e3640000

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

Reland "Use GL_COMMANDS_ISSUED_CHROMIUM query for shared memory GpuMemoryBuffers" by sunnyps@chromium.org
https://chromium.googlesource.com/chromium/src/+/80d0a681332ba4c48d10e11f17d833eea89758ce
0.5085 → 3.042 (+2.533)

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

Benchmark documentation link:
  https://bit.ly/rendering-benchmarks

mean_pixels_approximated_tbmv2 increased slightly (0.3% to 1.1%), but mean_pixels_checkerboarded_tbmv2 decreased (51.6% to 45.9%).  That's a good thing because we're now rendering high res tiles and a few more low res tiles instead of checkerboarding due to the increase in throughput.

ericrk@ FYI the above improvement is on Nexus 5