Re: Increased latency after setting row_cache_size_in_mb

2018-02-06 Thread mohsin k
l Singh > rahul.si...@anant.us > > Anant Corporation > > On Feb 6, 2018, 8:50 AM -0500, mohsin k , > wrote: > > Thanks, Jeff, will definitely check the trace. Also, one strange thing I > noticed, with number of threads till '64', the latency is around 3ms but as &

Re: Increased latency after setting row_cache_size_in_mb

2018-02-06 Thread mohsin k
g cross wan and the other dc is > 10-20ms away). > > If the latency is seen in p99 but not p50, you can almost always > speculatively read from another coordinator (driver level speculation) > after a millisecond or so. > > -- > Jeff Jirsa > > > On Feb 5, 2018,

Re: Increased latency after setting row_cache_size_in_mb

2018-02-05 Thread mohsin k
p lifecycle and so on > > For read heavy workflow it is sometimes advised to reduce chunk_length_in_kb > from the default 64kb to 4kb, see if it helps ! > > On 5 February 2018 at 13:09, mohsin k wrote: > >> Hey Rahul, >> >> Each partition has around 10 cluster keys

Re: Increased latency after setting row_cache_size_in_mb

2018-02-05 Thread mohsin k
Hey Rahul, Each partition has around 10 cluster keys. Based on nodetool, I can roughly estimate partition size to be less than 1KB. On Mon, Feb 5, 2018 at 5:37 PM, mohsin k wrote: > Hey Nicolas, > > My goal is to reduce latency as much as possible. I did wait for warmup. > The

Re: Increased latency after setting row_cache_size_in_mb

2018-02-05 Thread mohsin k
ugh. > > Rahul > > On Feb 5, 2018, 6:52 AM -0500, mohsin k , > wrote: > > Hi, > > I have been looking into different configurations for tuning my cassandra > servers. So, initially I loadtested server using cassandra-stress tool, > with default configs and then tuning on