|Compression on client side vs server side||Ben McCann||4/2/12 8:42 AM|
I was curious if I compress my data on the client side with Snappy whether there's any difference between doing that and doing it on the server side? The wiki said that compression works best where each row has the same columns. Does this mean the compression will be more efficient on the server side since it can look at multiple rows at once instead of only the row being inserted? The reason I was thinking about possibly doing it client side was that it would save CPU on the datastore machine. However, does this matter? Is CPU typically the bottleneck on a machine or is it some other resource? (of course this will vary for each person, but wondering if there's a rule of thumb. I'm making a web app, which hopefully will store about 5TB of data and have 10s of millions of page views per month)
|RE: Compression on client side vs server side||Jeremiah Jordan||4/2/12 8:53 AM|
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 because there is less to read from disk. In many cases it is actually faster to read a compressed file from disk and decompress it, then to read an uncompressed file from disk.
See Ed's post:
"Cassandra compression is like more servers for free!"
|Re: Compression on client side vs server side||Martin Junghanns||4/2/12 8:54 AM|
how do you select between client- and serverside compression? i'm using
|Re: Compression on client side vs server side||Ben McCann||4/2/12 9:03 AM|
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.
|Re: Compression on client side vs server side||Віталій Тимчишин||4/3/12 7:50 AM|
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) Any server utility operations, like repair or move (not sure for the latter) will decompress/compress
So, client side decompression looks way cheapier and can be very efficient for long columns.
Best regards, Vitalii Tymchyshyn
2012/4/2 Jeremiah Jordan <JEREMIA...@morningstar.com>