Live data from Hacker News

Turns Out AI Is Not Good at Database Transaction Scheduling

adrs-ucb.notion.site

1–10 of 11 posts

Re: Turns Out AI Is Not Good at Database Transaction Scheduling

#2
We 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

#3
post #2

We 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

#10
post #9

Transactions 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.
Post reply on HN