Limit or disable batch size optimization for individual migrations
We use batch size optimization to accomplish batched background migrations as quickly as possible. We also intend to throttle them based on database metrics in #329769, so we can scale back when the database is lagging behind our changes.
However, due to data distribution or the particular nature of certain problems, we might want to control the batch size optimization on an individual migration level.
I think we should support both:
- disabling batch size optimization on individual migrations
- specifying maximum caps for optimization on individual migrations
✅
Eventually if our database feedback and algorithm are advanced enough we may not need this, but it would still be useful to have this in the meantime.
Edited by Diogo Frazão