Hi there,
In Cassandra 2, there were recommendations not to exceed 100MB per partition, I have been told that is not the case with Cassandra 3 but its recommended to keep it small due to sync performance should partition be too big.
Question is, how big is too big and how can we measure big partition impact on sync/replication latency should partition grow?
@marcin_175159 there are no absolutes and the same 100MB partition size recommendation applies but you can have partitions larger than that -- it all depends on your use case, data model, access patterns, etc.
The only way you can determine the impact of large partitions is by performing exhaustive testing with production-like workloads. Cheers!
Hi @Erick Ramirez thanks for that, but is there some way to measure how sync/timings are affected while partition size increases? Can nodetool handle it?
You measure the performance of your cluster by performing read/write load tests on production-like data. Not sure what you mean by "can nodetool handle it?".
+1 with what @Erick Ramirez just said:
Thanks @Cedrick Lunven but how can we measure impact of size on scanning and stream performance/time? Is there something nodetool can report?
You measure it by monitoring read latencies while running load tests that simulate production-like data and production-like access patterns. Cheers!
4 People are following this question.
