A question - @GuyCarmin We have systems in production which are 27-36 nodes for example (m6g.4xlarge). What sort of size cut should I be able to expect from a Scylla DB system (very roughly)? We tend to currently get limited by the CPU rather than I/O. For Scylla, is it that much more CPU efficient that it is way more likely to be limited by I/O instead of CPU thus the recommendation for instances that use SSDs?
gcollins
5
Related topics
| Topic | Replies | Views | Activity | |
|---|---|---|---|---|
| Use case for replacing Cassandra with ScyllaDB, read and write performance | 0 | 279 | July 9, 2024 | |
| ScyllaDB's read path vs. Cassandra's and performance when using HDD vs SSD | 4 | 832 | December 5, 2022 | |
| ScyllaDB mass insertion advice needed | 1 | 291 | October 21, 2024 | |
| Testing ScyllaDB performance issue with Kubernetes clusters, using containers | 0 | 156 | January 20, 2025 | |
| Performance issue, throughput drop and latency increase | 0 | 257 | November 28, 2024 |