We are using client-side compression because of next points. Can you
confirm they are valid?
1) Server-side compression uses replication factor more CPU (3 times more
with replication factor of 3).
2) Network is used more by compression factor (as you are sending
uncompressed data over the wire).
4
Thanks Jeremiah, that's what I has suspected. I appreciate the
confirmation.
Martin, there's not built-in support for doing compression client side, but
it'd be easy for me to do manually since I just have one column with all my
serialized data, which is why I was considering it.
On Mon, Apr 2,
Hi,
how do you select between client- and serverside compression? i'm using
hector and i set compression when creating a cf, so the compression
executes when inserting the data "on the server" oO
greetings, martin
Am 02.04.2012 17:42, schrieb Ben McCann:
Hi,
I was curious if I compress my
The server side compression can compress across columns/rows so it will most
likely be more efficient.
Whether you are CPU bound or IO bound depends on your application and node
setup. Unless your working set fits in memory you will be IO bound, and in
that case server side compression helps be
