Telemetry 101
Telemetry has become the framework for cross-(chrome)-platform performance testing. Telemetry is a python wrapper around of the DevTools Remote Debugging Protocol. Telemetry abstracts launching, connecting, and opening a page in whatever underlying platform Chrome is running, fetching data via the Inspector timeline and traces, loading Chrome with arbitrary flags, and using Web Page Replay to cache real-world websites so they don’t change when used in benchmarks.
Core Principles
Write one performance test that can trivially run on all platforms [Mac/Win/Linux, CrOS, Android] for both Chrome and ContentShell
Run on browser binaries, without having to build the browser yourself
Use WebPageReplay to get repeatable test results
Run on non-chrome browsers for comparative studies (not yet implemented)
Clean architecture for writing benchmarks that keeps measurements and use cases separate
The system I’m using to generate the blog is called Octopress by Brandon Mathis, which is a framework around Jekyll. You can run it wherever you like (locally, or even on your server), and it will generate an entirely static web site for you, and even rsync it to where you’re hosting from.
If you’re wondering about whether to “bake” your own blog or site, I can recommend these three posts by Brent Simmons on why you should consider it. I can also highly recommend Octopress as the means of doing it.