Track how long it takes us to update the pages configuration
In !60 (merged), we added a benchmark and some performance optimizations around loading the Pages configuration from disk, which involves scanning every directory in the -pages-root
and reading every config.json
file in the tree.
We won't know how much of an effect this will have on production because we're not tracking how long that process takes, although we do track the time it was last done.
Let's add a metric for "how long did this take?", along with a metric for "how many times did this happen?"