4 ms·
It seems like "Self-Driving" to the authors means simply that it has a query optimizer using ML. I would counter that idea by suggesting that a more foolproof
by etaioinshrdlu 6y ago
It seems like "Self-Driving" to the authors means simply that it has a query optimizer using ML.
I would counter that idea by suggesting that a more foolproof database would also incorporate truly solid auto-scaling, and global replication, so that one can just throw immense amounts of data into tables, while retaining fast CRUD operations worldwide, without any DBA support required. A little bit like the direction CockroachDB and TiDB are headed, perhaps.
- jasonwatkinspdx 6y agoThis is part of an existing line of research going back decades. Fully self tuning database engines have proven to be a lot more tricky than you'd assume. It's not the same thing as horizontal scalability. If you want to build a Spanner/Cockroach/Ti style system, you'll face the questions they're examining in detail in your per node storage engine. The empirical evaluation paper in particular is interesting and useful stuff.
- apavlo 6y ago> It seems like "Self-Driving" to the authors means simply that it has a query optimizer using ML. Nope. Please see this article for my definition of self-driving: http://www.cs.cmu.edu/~pavlo/blog/2018/04/what-is-a-self-driving-database-management-system.html http://www.cs.cmu.edu/~pavlo/blog/2018/04/what-is-a-self-dri...
- brainless 6y agoI had come across peloton before in my research in this domain as I mentioned in another comment that I am building a product with similar long-term goals. Congrats on the work, would love to see schema also take care of.
- brainless 6y agoDoes not seem like that to me at all. Just their about page says they are taking care of the entire deployment and lifespan of the database - indexes to hardware capacity. I would like them to take care of schema too.