3 ms·
> addressing your caching point so from my understanding - the learning part isn't frequently used and caching, it's (attempting to be) generalized workload le
by aerioux 10y ago
> addressing your caching point
so from my understanding - the learning part isn't frequently used and caching, it's (attempting to be) generalized workload learning, the part of understanding that every DBA should do but usually doesnt.
If that is successfully and is even marginally able to predict workload skews, then the scheduling of operations can be significantly more efficient -- you're essentially reducing entropy in your database massively.
- gigatexal 10y agoAny team of database admins/engineers worth their salary plans for capacity, fixes inefficient queries, And works with development on future goals for what they want out of the database layer.
- michaelmior 10y agoAnd you don't think it would be valuable to be able to automate many of those tasks?
- gigatexal 10y agoI agree it would but my premise is that I doubt it can be.