Re: Retrieving a column from a fat row vs retrieving a single row

2011-06-10 Thread Héctor Izquierdo Seliva
I think I will follow the advice of better balancing and I will split the index into several pieces. Thanks everybody for your input!

Re: Retrieving a column from a fat row vs retrieving a single row

2011-06-09 Thread aaron morton
Don't forget that reading at ONE may not mean that only 1 replica is involved in the request. Any get or multiget (not range scan) read that runs with ReadRepair enabled will be sent to all UP replicas. If the RR is disabled it will only be sent to as many replicas as needed for the CL. For CL

Re: Retrieving a column from a fat row vs retrieving a single row

2011-06-09 Thread Richard Low
2011/6/9 Héctor Izquierdo Seliva : > Yeah, but if I have RF=3 then there are three nodes that can answer the > request right? Yes, if you're happy to read ConsistencyLevel.ONE.

Re: Retrieving a column from a fat row vs retrieving a single row

2011-06-09 Thread Héctor Izquierdo Seliva
El jue, 09-06-2011 a las 13:28 +0200, Richard Low escribió: > Remember also that partitioning is done by rows, not columns. So > large rows are stored on a single host. This means they can't be load > balanced and also all requests to that row will hit one host. Having > separate rows will allow

Re: Retrieving a column from a fat row vs retrieving a single row

2011-06-09 Thread Richard Low
Remember also that partitioning is done by rows, not columns. So large rows are stored on a single host. This means they can't be load balanced and also all requests to that row will hit one host. Having separate rows will allow load balancing of I/Os. -- Richard Low Acunu | http://www.acunu.c

Re: Retrieving a column from a fat row vs retrieving a single row

2011-06-08 Thread aaron morton
Just to make things less clear, if you have one row that you are continually writing it may end up spread out over several SSTables. Compaction helps here to reduce the number of files that must be accessed so long as is can keep up. But if you want to read column X and the row is fragmented ove

Re: Retrieving a column from a fat row vs retrieving a single row

2011-06-08 Thread Peter Schuller
> As far as I know, to read a single column cassandra will deserialize a > bunch of them and then pick the correct one (64KB of data right?) Assuming the default setting of 64kb, the average amount deserialized given random column access should be 8 kb (not true with row cache, but with large rows

Retrieving a column from a fat row vs retrieving a single row

2011-06-08 Thread Héctor Izquierdo Seliva
Hi, I have an index I use to translate ids. I usually only read a column at a time, and it's becoming a bottleneck. I could rewrite the application to read a bunch at a time but it would make the application logic much harder, as it would involve buffering incoming data. As far as I know, to read