3 ms·
"A Cassandra compatible NoSQL column store, at 1MM transactions/sec per server." Personal pet-peeve of mine. Using "TPS" or "Transactions/sec" to measure somet
by jhugg 11y ago
"A Cassandra compatible NoSQL column store, at 1MM transactions/sec per server."
Personal pet-peeve of mine. Using "TPS" or "Transactions/sec" to measure something that is in no way transactional. Maybe ops/sec, reads/sec, updates/sec, or something...
- JoeAltmaier 11y agoAdd my pet peeve: not listing latency stats. Big Tables does millions of ops/sec but it can take 5(!) seconds to complete one. That's the stat that matters to customers.
- lucindo 11y agohttp://www.scylladb.com/technology/cassandra-vs-scylla-latency-benchmark/ http://www.scylladb.com/technology/cassandra-vs-scylla-laten...
- JoeAltmaier 11y agoThanks!
- rakoo 11y ago> The test hardware configuration includes: > 1 DB server (Cassandra / Scylla) The whole point of Cassandra is to run a cluster of servers to handle load at scale with minimal friction instead of having to buy a big single machine or spend all your time/money trying to run a clustered RDBMS. This test doesn't measure the correct thing.
- acconsta 11y agoCassandra's performance scales linearly with the number of nodes though, so per-node performance definitely matters. Probably not 10x, but probably not 1x either.