The big * in the explanation: Smaller file size footprint leads to better
disk cache, however decompression adds work for the JVM to do and increases
the churn of objects in the JVM. Additionally compression block sizes might
be 4KB while for some use cases a small row may be 200bytes. This means
t
Hi John,
I am trying again :)
The way I understand it is that compression gives you the advantage of
having to use way less IO and rather use CPU. The bottleneck of reads is
usually the IO time you need to read the data from disk. As a figure, we
had about 25 reads/s reading from disk, while
This article[1] cites gains in read performance can be achieved when
compression is enabled. The more I thought about it, even after reading the
DataStax docs about reads[2], I realized I do not understand how
compression improves read performance. Can someone provide some details on
this?
Is the
