I've done some basic data-driven profiling of options for my tower, but with so many settings/options it can be hard to find the ideal settings for a machine or user. What are some people's thoughts on a performance test-suite people can run to help identify what settings make the most sense. At a minimum I'm thinking the options listed https://www.pantsbuild.org/docs/using-pants-in-ci#tuning-resource-consumption-advanced would be nice to find-and-set. The implementation could be either standalone, or a backend users can opt-into, run, and then likely opt-out-of. Additionally, I think there is likely different settings that would be ideal for different workflows. For CI you're likely running on all files, whereas dev boxes are ideally running on subsets of the world. (This came up from thinking about

--batch-size

in https://github.com/pantsbuild/pants/pull/14186)