It would be useful to have a way to see how long it takes a patch to be processed by EWS (i.e., the elapsed time from when the patch is uploaded to when it has been built). It would be nice to see this for each flavor of EWS bot (Windows, Mac, Chromium, GTK, etc.). This would be helpful when trying to determine which EWS flavors need more hardware.
So you want the average time per patch? That's very easy to do for the commit-queues, but we'd have to add a second log message for the EWSes to support this. Right now each EWS only logs exactly once per patch. We'd need two logs to compute a time taken. http://queues.webkit.org/queue-status/gtk-ews
(In reply to comment #1) > So you want the average time per patch? Yes, please! If you wanted to get really fancy you'd show two numbers: average seconds until patch begins being processed by an EWS bot, and average time it takes for the processing to occur. (Summing the two would give you the end-to-end time.)
I've often wanted to know the average queue length. That's generally the metric I use to decide whether to spin up more instances.