Does raising max_tis_per_query reduce Airflow burst scheduling latency, or does it move the bottleneck to the metadata database?
When a large number of task instances become runnable simultaneously, Airflow's scheduler processes them in bounded batches controlled by max_tis_per_query ; at low concurrency this limit is invisible, but under a burst it can introduce queueing delay. The unresolved decision is whether increasing this batch size actually improves task start latency or simpl