Cluster Telemetry (https://www.chromium.org/developers/cluster-telemetry) allows to try a patch to src/ on top(10k) most popular webpages to see for possible performance regressions or gains.

This is supplemental to the micro-benchmarks which Perf team maintains.

This issue is to try to run an LTO build of Chrome with Cluster Telemetry. Most likely, we'll find that a slave would die due to OOM, but that will only give us one more data point for the planned hardware upgrades: https://crbug.com/598011

I will keep this bug in my queue, but there're bots to fix, so I won't immediately start working on this.