You are viewing a plain text version of this content. The canonical link for it is here.

Posted to user@cassandra.apache.org by Grzegorz Pietrusza <gp...@gmail.com> on 2022/10/25 15:26:52 UTC

concurrent sstable read

HI all

I can't find any information about how cassandra handles reads involving
multiple sstables. Are sstables read concurrently or sequentially? Is read
latency directly connected to the number of opened sstables?

Regards
Grzegorz

Re: concurrent sstable read

Posted by Jeff Jirsa <jj...@gmail.com>.

Sequentially, and yes - for some definition of "directly" - but not just
because it's sequential, but also because each sstable has cost in reading
(e.g. JVM garbage created when you open/seek that has to be collected after
the read)

On Tue, Oct 25, 2022 at 8:27 AM Grzegorz Pietrusza <gp...@gmail.com>
wrote:

> HI all
>
> I can't find any information about how cassandra handles reads involving
> multiple sstables. Are sstables read concurrently or sequentially? Is read
> latency directly connected to the number of opened sstables?
>
> Regards
> Grzegorz
>