Adaptive Thread Pool
Aurora's thread pool doesn't look quite like MySQL's. With features like multiplexed connections and the ability to handle over 5,000 concurrent sessions, Aurora's thread pool means you don't have to use connection pooling. It's more scalable than MySQL's thread pooling, and when you use it, you have one fewer thing you need to worry about on the database. Overall, Aurora's thread pool is a more "modern" system. It's what you would expect to see from a database created today.wow pic.twitter.com/KeVY5VBEMS
— Preetam (@PreetamJinka) December 21, 2016
Transactional DDL
DDL refers to operations like ALTERs. It's not just transactional, but online too. This is the benefit of using log-structured storage.@PreetamJinka what would you like to know ? Yes we do have transactional DDL.
— SaileshKrishnamurthy (@saileshkrish) May 25, 2016
This isn't actually documented anywhere we've seen, but it's a definite benefit to know about.
A Rewritten Query Cache
Aurora's rewritten query cache could represent a major difference in how it should be run vs. MySQL. MySQL's query cache is frequently the cause of server stalls, as we've seen with our Adaptive Fault Detection. It can cause more harm than good, and there's a reason why it's been disabled by default in MySQL for more than four years. Aurora's brand new query cache makes the feature worth revisiting. This comes with the caveat that we haven't yet investigated Aurora's query cache--if you choose to use it, you should still benchmark it both enabled/disabled with your workload, then act according to the results you see.@PreetamJinka @VividCortex Don't turn off the query cache with Aurora ! We rewrote it completely :-)
— SaileshKrishnamurthy (@saileshkrish) January 26, 2017
