Hi, This seems like a significant level of technical complication/debt relative to even a 1.5x/2x gain (which as noted is only in certain workloads). Given airflow scheduling code in general is not something one could describe as simple, introducing large amounts of static code that lives in stored procs seems unwise.If at all possible making this interface pluggable and provided via provider would be the saner approach in my opinion.
On Tue, Sep 23, 2025 at 11:16 AM asquator <[email protected]> wrote: > Hello, > > A new approach utilizing stored SQL functions is proposed here as a > solution to unnecessary processing/starvation: > > https://github.com/apache/airflow/pull/55537 > > Benchmarks show an actual improvement in queueing throughput, around > 1.5x-2x for the workloads tested. > > Regarding DB server load, I wasn't able to note any difference so far, we > probably have to run heavier jobs to test that. Looks like a smooth line to > me. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
