epriestley df3c937dab Record lock timing information on PushEvents ... Summary: Depends on D19249. Ref T13109. Add timing information to the `PushEvent`: - `writeWait`: Time spent waiting for a write lock. - `readWait`: Time spent waiting for a read lock. - `hostWait`: Roughly, total time spent on the leaf node. The primary goal here is to see if `readWait` is meaningful in the wild. If it is, that motivates smarter routing, and the value of smarter routing can be demonstrated by looking for a reduction in read wait times. Test Plan: Pushed some stuff, saw reasonable timing values in the table. Saw timing information in "Export Data". Maniphest Tasks: T13109 Differential Revision: https://secure.phabricator.com/D19250		2018-03-22 13:46:01 -07:00
..
autopatches	Record lock timing information on PushEvents	2018-03-22 13:46:01 -07:00
patches	Remove a very old Herald garbage collection migration	2018-01-26 10:54:37 -08:00
quickstart.sql	Revert quickstart for tables with native FULLTEXT indexes to MyISAM	2017-09-12 12:24:23 -07:00
stopwords.txt	Provide a setup warning about using the default MySQL stopword file	2014-08-13 15:34:09 -07:00
stopwords_myisam.txt	Show users how fulltext search queries are parsed and executed; don't query stopwords or short tokens	2017-04-12 19:07:54 -07:00