Re: Optimal value for concurrent_reads for a single NVMe Disk

2016-09-20 Thread Romain Hardouin
Hi, You should make a benchmark with cassandra-stress to find the sweet spot. With NVMe I guess you can start with a high value, 128? Please let us know the results of your findings, it's interesting to know if we can go crazy with such pieces of hardware :-) Best, Romain Le Mardi 20 septem

Optimal value for concurrent_reads for a single NVMe Disk

2016-09-20 Thread Thomas Julian
Hello, We are using Cassandra 2.1.13 with each node having a NVMe disk with the configuration of Total Capacity - 1.2TB, Alloted Capacity - 880GB. We would like to increase the default value of 32 for the param concurrent_reads. But the document says "(Default: 32)note For workloads with