>The Scylla design, right, is based on a modern shared-nothing approach. Scylla runs multiple engines, one per core, each with its own memory, CPU and multi-queue NIC. We can easily reach 1 million CQL operations on a single commodity server. In addition, Scylla targets consistent low latency, under 1 ms, for inserts, deletes, and reads. Interesting. From: http://www.scylladb.com/technology/architecture/
So on virtualized hardware, namely AWS, I'm sure the benchmarks won't be so magnificent. Needing a dedicated nic per core is a big deal unless you're at a pretty large scale.
ScyllaDB: Drop-in replacement for Cassandra that claims to be 10x faster
11–20 of 99 posts
Re: ScyllaDB: Drop-in replacement for Cassandra that claims to be 10x faster
#12Broadly speaking, this is the correct style of architecture for a database engine on modern hardware. It is vastly more efficient in terms of throughput than the more traditional architectures common in open source. It also lends itself to elegant, compact implementations. I've been using similar architectures for several years now.
While I have not benchmarked their particular implementation, my first-hand experience is that these types of implementations are always at least 10x faster on the same hardware than a nominally equivalent open source database engine, so the performance claim is completely believable. One of my longstanding criticisms of open source data infrastructure has always been the very poor operational efficiency at a basic architectural level; many closed source companies have made a good business arbitraging the gross efficiency differences.
Re: ScyllaDB: Drop-in replacement for Cassandra that claims to be 10x faster
#13Re: ScyllaDB: Drop-in replacement for Cassandra that claims to be 10x faster
#14will this be the next docker in the nosql database?
Re: ScyllaDB: Drop-in replacement for Cassandra that claims to be 10x faster
#15>The Scylla design, right, is based on a modern shared-nothing approach. Scylla runs multiple engines, one per core, each with its own memory, CPU and multi-queue NIC. We can easily reach 1 million CQL operations on a single commodity server. In addition, Scylla targets consistent low latency, under 1 ms, for inserts, deletes, and reads. Interesting. From: http://www.scylladb.com/technology/architecture/
So on virtualized hardware, namely AWS, I'm sure the benchmarks won't be so magnificent. Needing a dedicated nic per core is a big deal unless you're at a pretty large scale.
Just to pull an example from memory, the ubiquitous Intel 82599 10GbE NIC silicon has up to 128 TX and RX queues in hardware. IIRC, these are bundled in pairs for direct access in virtualized environments, so in principle you could have 64 virtual cores each with their own dedicated physical hardware queue. This is almost certainly what they were talking about. That is the whole point of this feature in Ethernet silicon; it gives cores (virtual or physical) dedicate network hardware off a single NIC.
Re: ScyllaDB: Drop-in replacement for Cassandra that claims to be 10x faster
#16Has it been through Jepsen yet?
Re: ScyllaDB: Drop-in replacement for Cassandra that claims to be 10x faster
#17Numbers look great, but so do /dev/null's. What guarantees does it make? Has it been through Jepsen yet?
Re: ScyllaDB: Drop-in replacement for Cassandra that claims to be 10x faster
#18Very nice. Broadly speaking, this is the correct style of architecture for a database engine on modern hardware. It is vastly more efficient in terms of throughput than the more traditional architectures common in open source. It also lends itself to elegant, compact implementations. I've been using similar architectures for several years now. While I have not benchmarked their particular implementation, my first-han…
Re: ScyllaDB: Drop-in replacement for Cassandra that claims to be 10x faster
#19Re: ScyllaDB: Drop-in replacement for Cassandra that claims to be 10x faster
#20Very nice. Broadly speaking, this is the correct style of architecture for a database engine on modern hardware. It is vastly more efficient in terms of throughput than the more traditional architectures common in open source. It also lends itself to elegant, compact implementations. I've been using similar architectures for several years now. While I have not benchmarked their particular implementation, my first-han…
Agreed, but which architectural features are you referring to?
"The Scylla design, right, is based on a modern shared-nothing approach. Scylla runs multiple engines, one per core, each with its own memory, CPU and multi-queue NIC."