Turns Out AI Is Not Good at Database Transaction Scheduling
adrs-ucb.notion.site
Turns Out AI Is Not Good at Database Transaction Scheduling
1–10 of 11 posts
Re: Turns Out AI Is Not Good at Database Transaction Scheduling
#2We modelled using Redshift scheduling automation, that suggested a welcome 20% improvement.
We applied it and it run 20% slower.
As it runs it is supposed to learn how to optimise scheduling. Not sure how it gets over the burst at month, quarter, and year end.
Re: Turns Out AI Is Not Good at Database Transaction Scheduling
#3We modelled using Redshift scheduling automation, that suggested a welcome 20% improvement. We applied it and it run 20% slower. As it runs it is supposed to learn how to optimise scheduling. Not sure how it gets over the burst at month, quarter, and year end.
What did you use to try to optimize scheduling?
Re: Turns Out AI Is Not Good at Database Transaction Scheduling
#4turns out DB transactions are a hard problem...
Re: Turns Out AI Is Not Good at Database Transaction Scheduling
#5I wonder what the optimal for these workloads are?
Re: Turns Out AI Is Not Good at Database Transaction Scheduling
#6For the offline problem, AI found a new solution that was 34% faster. Interesting results!
Re: Turns Out AI Is Not Good at Database Transaction Scheduling
#7What about other use cases
Re: Turns Out AI Is Not Good at Database Transaction Scheduling
#8Seems like AI hype
Re: Turns Out AI Is Not Good at Database Transaction Scheduling
#9Transactions seem like a hard problem for scheduling, wonder how the authors got this to work in the original paper?
Re: Turns Out AI Is Not Good at Database Transaction Scheduling
#10Transactions seem like a hard problem for scheduling, wonder how the authors got this to work in the original paper?
As described in our VLDB paper (https://www.vldb.org/pvldb/vol17/p2694-cheng.pdf), we had to implement a number of optimizations and integrate scheduling with CC to get good performance.