High latency at table level could be a result of no of factors.
High tombstones
GC
Bloom filter fp
I/O bottleneck
Insufficient cache or threads
Since your partion size is not a problem here, try running major
compaction on this table.
Also you can turn on caching for this table.
As mentioned
17ms read latency for the 50th percentile is actually a pretty high latency
in my experience, I prefer to see the 75th percentile read latency to be
around 1-2ms. Of course it depends on your use case and what your
performance objectives are.
On Thu, Apr 29, 2021 at 7:05 AM Kane Wilson wrote:
It does imply the SSTables are being read - how big is your data size and
how much memory on the nodes? It's certainly possible to get low latencies
despite many SSTables, but I'd expect small read sizes paired with a lot of
memory.
raft.so - Cassandra consulting, support, managed services
On
The table has 24 sstables with size tiered compaction, when I run nodetool
tablehistograms I see 99% percentile of the queries are showing up 24 as
the number of sstables. But the read latency is very low, my understanding
from the tableshistograms's sstable column is - it shows how many sstables
