5 ms·
Even if it is fair I only get two points from this article (and their product page): * A system which holds all data in memory is faster than a system which us
by sgift 16y ago
Even if it is fair I only get two points from this article (and their product page):
* A system which holds all data in memory is faster than a system which uses memory and disks. True, but not really news.
* If you leave out features your implementation can be faster (e.g. they only support transactions which span a single stored procedure). Again .. no news here.
Something else I've missed?
- JoachimSchipper 16y agoNot really, but do note that it is spectacularly faster.
- rayval 16y ago* A system that is designed for mostly disk will run faster when run in memory, but won't be as fast as one designed from the outset for in-memory operation. * Leaving out features is harder than adding features, because you have to judiciously decide which ones to leave out. A large bushel o' features can have many different subsets, and only some of these subsets are worthwhile.
- jhugg 16y agoI like this point. At VoltDB, we like to think we've removed a different set of features than many other scalable solutions, leaving a product that is useful for a set of problems that might not have a great option right now. That said, VoltDB's architecture was built for in-memory and horizontal scaling from day 1. Based on hstore (http://hstore.cs.brown.edu/ http://hstore.cs.brown.edu/), it's not simply a removal of what's in existing systems.