Hi Abdul,
That all depends on the cluster, so it really is best to experiment.
By adding more threads you will use more of the system resources, so before you
start you need to know if there is spare capacity in the CPU usage and the disk
throughput. If there is spare capacity then increase the
Do we have any recommendations on concurrents reads ans writes settings?
Mine is 18 node 3 dc cluster with 20 core cpu
On Wednesday, April 10, 2019, Anthony Grasso
wrote:
> Hi Abdul,
>
> Usually we get no noticeable improvement at tuning concurrent_reads and
> concurrent_writes above 128. I gene
Hi Abdul,
Usually we get no noticeable improvement at tuning concurrent_reads and
concurrent_writes above 128. I generally try to keep current_reads to no
higher than 64 and concurrent_writes to no higher than 128. In creasing the
values beyond that you might start running into issues where the ke
Yes the queries are all select queries as they are more of read intensive
app.
Last night i rebooted cluster and today they are fine .(i know its
temporary) as i still is all time blocked values.
I am thinking of incresiing concurrent reads and writes to 256 and native
transport threads to 256 and
Hi Abdul,
When I have seen dropped messages, I normally double check to ensure the node
not CPU bound.
If you have a high CPU idle value, then it is likely that tuning the thread
counts will help.
I normally start with concurrent_reads and concurrent_writes, so in your case
as reads are bein
In my cluster, I have it at 4096. I think you can start with 1024 and check
if you have no native requested blocked.
I believe this parameter depends on the cluster traffic
Cheers
Jean Carlo
"The best way to predict the future is to invent it" Alan Kay
On Tue, Apr 9, 2019 at 7:59 PM Abdul Pat
