| |||||||||||||
A report from OpenSQLCampA report from OpenSQLCampPosted Nov 3, 2010 15:47 UTC (Wed) by rbetts@gweep.net (subscriber, #21779)Parent article: A report from OpenSQLCamp
Wonderful summary. Thanks for taking the time to write about the conference.
To put some (very course) numbers around the VoltDB latency / throughput tradeoffs - volt typically achieves ~10ms latencies from relatively idle to 80% or so of max throughput capacity (possibly 100k's of multi-sql-statement stored procedures per second).
Ryan.
(Log in to post comments)
A report from OpenSQLCamp Posted Nov 3, 2010 17:41 UTC (Wed) by nteon (subscriber, #53899) [Link]
what are typical latencies for a traditional RDBMS like Postres or Mysql?
A report from OpenSQLCamp Posted Nov 4, 2010 17:27 UTC (Thu) by kjp (subscriber, #39639) [Link]
VoltDB is interesting. I'm wondering if two postgres databases could instead use eachother's RAM instead of a transaction log, to have very high transaction rates.
It's sync replication but only to RAM. Checkpoints can occur whenever. So you get higher availability than a single server and more speed due to transactions just hitting RAM.
|
|||||||||||||