dorlaor

6 ms·

1.
by dorlaor 2y ago
Some additional nuggets by ScyllaDB co-founder: - Discord couldn't complete repair with Cassandra. Not the case with Scylla - Scylla has a lot in common with Cassandra, from a good reason, like the LSM tree, compaction etc. However, Sc
2.
by dorlaor 3y ago
Most users of ScyllaDB/Cassandra use quorum or local_quorum
3.
by dorlaor 4y ago
My understanding is that the new Rust coalescing will make the situation on-par with the new go driver. However, in the second part of the blog there is a no-coalescing test where go is still faster and allocates less memory. I'm sure
4.
The Pinecone(pinecone.io)
5 points by dorlaor 4y ago|0 comments
5.
by dorlaor 5y ago
GSI, LSI are fully supported already. Backup is fully supported too (but not identical to DynamoDB). TTL is in final development mode. So yes, everything is planned to be fully supported
6.
by dorlaor 6y ago
Shard per core has challenges. Scylla solves it partially by making the client shard aware (topology aware), so the client submits requests directly to the right cpu core using a different port. This way no data gets blocked due to hot keys
7.
by dorlaor 7y ago
At Scylla we initially defined a new filesystem which adheres shard-per-core and thus a single physical hyperthread has the sole access to the data and thus there is no contention. While it will be better than current XFS, we've made a
8.
by dorlaor 7y ago
Seastar.io is another one, it's an async engine that utilizes all of the cores in a modern system and is the heart of Scylla's DB. However, it's complex to use it correctly
9.
by dorlaor 7y ago
The advantage of in-memory it's also its biggest disadvantage - it's costly. NVMe can serve almost as fast as ram and is 100x cheaper. Scylla offers single digit msec (usually 1msec) 99% latency and way more cost effective
10.
by dorlaor 7y ago
We at Scylla tune the kernel, drives, stride, clock source automatically and benchmark the disk to figure out what's its maximum parallelism so it won't queue (we can saturate 8 NVMe) and we'll do the queuing within the DB&#x
11.
by dorlaor 7y ago
With LSM approach (log structured merge tree) we have at Scylla, we make all the writes batched/sequential and receive an awesome boost. Some reads can be sequential too if you scan through the clustering keys.
12.
Reducing latency spikes by tuning the CPU scheduler(scylladb.com)
12 points by dorlaor 10y ago|1 comments
13.
by dorlaor 11y ago
It's planned. However, I don't believe we'll pass it today. We're targeting GA for Jan and we'll give it our best shot.
14.
by dorlaor 11y ago
Latency is great - http://www.scylladb.com/technology/cassandra-vs-scylla-laten... and we promise to improve it further. The client API is CQL. We have thrift too but it's not mature enough. We'll invest in