Love things like this. Here's a screenshot expanded version of our staff bar on GitHub.com: http://cl.ly/image/0O0N183x2F44 http://cl.ly/image/0O0N183x2F44 M

Love things like this. Here's a screenshot expanded version of our staff bar on GitHub.com: http://cl.ly/image/0O0N183x2F44 http://cl.ly/image/0O0N183x2F44 Most of those numbers are clickable. The graphs button on the left links to a flame graph (https://www.google.com/search?q=flame+graph https://www.google.com/search?q=flame+graph) Ruby calls of the page. The microscope button is a sorted listing of CPU time and idle time by file that went into the page's render. The template number links to a timing breakdown of all the partials that went into the view. The SQL timing links to a breakdown of MySQL queries for that page, calling out N+1 queries, slow queries, or otherwise horrible database decisions. Depending on the page, we'll also have numbers for duration and queries spent in redis, elasticsearch, and gitrpc. Our main github.com stuff is pretty tied into our stack, but one of our employees, Garrett Bjerkhoel, extracted a lot of this into peek, a very similar implementation of what we have on GitHub. We use peek in a ton of our smaller apps around the company. Here's the org: https://github.com/peek https://github.com/peek