Bots are probably responsible for hits on expensive pages that are making mongodb quite busy. We should either block those urls or put them behind login.
|Open||dpifke||T158837 Consolidate performance website and related software|
|Invalid||None||T159351 Investigate which xhgui pages are expensive and block them from public access|
Per T161196, it turns out all these views work quite well as long we do don't pump it full with too large of a data sets. I've disabled the production sampling for now and cleared the database per T161196: tungsten is out of space on /srv.
We should be able to keep manual XMD profiles for a near-indefinite period of time given the 1TB space available. If we do want to enabled production sampling again, we should clear these non-XMD profiles within a set time period (e.g. a nightly cron that deletes all non-XMD entries in mongo.xhprof.results more than 7 days old or something like that).
Given the db now performs properly we don't need to disable any urls or restrict access to avoid overload.