3 ms·
Turns Out AI Is Not Good at Database Transaction Scheduling
- pos456 11mo agoFor the offline problem, AI found a new solution that was 34% faster. Interesting results!
- zeristor 11mo agoWe 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.
- accheng 11mo agoWhat did you use to try to optimize scheduling?
- qat321 11mo agoturns out DB transactions are a hard problem...
- taqpos 11mo agoI wonder what the optimal for these workloads are?
- gfhsad 11mo agoWhat about other use cases
- accheng 11mo agoCheck out our blog series here: ucbskyadrs.github.io!
- kap901 11mo agoSeems like AI hype
- pakt1 11mo agoTransactions seem like a hard problem for scheduling, wonder how the authors got this to work in the original paper?
- accheng 11mo agoAs described in our VLDB paper (https://www.vldb.org/pvldb/vol17/p2694-cheng.pdf 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.