cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ben McCann <...@benmccann.com>
Subject Re: Compression on client side vs server side
Date Mon, 02 Apr 2012 16:03:04 GMT
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, 2012 at 8:54 AM, Martin Junghanns <m.junghanns@googlemail.com
> wrote:

> 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 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)
>>
>> Thanks,
>> Ben
>>
>>
>

Mime
View raw message