Re:DeepDB – High-performing transactional and analytic database
by maxdemarzi on Sunday February 16, 2014 @05:38PM
(#7249667)
Seems to be targeted as a replacement for InnoDB, slides with actual "meat" on them => https://portland2013.drupal.org/sites/default/files/slides/B...
As a more technical nitpick, "high availability" does not mean fast restarts. It means never goes down. The design as described is not a high availability architecture.
Bonus observation: if you assert your database engines uses extensive fine-grained locking, don't show a chart with 24 cores at ~100% utilization and call it "efficient". This is what you would expect to see for a poorly designed and very inefficient implementation for this type of architecture. You can be burning all of your CPU and getting very little throughput. A credible presentation would have demonstrated that system throughput scales linearly with the number of cores (unlikely given the description of their internals).