Some big systems using Cassandra's counters were built (such as Rainbird:
http://www.slideshare.net/kevinweil/rainbird-realtime-analytics-at-twitter-strata-2011)
and seem to be doing great job.
If you are concerned with performance, then maybe using memory-based store
(such as Redis) will better s
nks for putting this up - sorry I missed your post the other week. I
> would be real curious as to your results if you added a prepared statement
> for those inserts.
>
>
> On Tue, Aug 20, 2013 at 9:14 AM, Przemek Maciolek wrote:
>
>> I had similar issues (sent a note on the li
I had similar issues (sent a note on the list few weeks ago but nobody
responded). I think there's a serious bottleneck with using wide rows and
composite keys. I made a trivial benchmark, which you check here:
http://pastebin.com/qAcRcqbF - it's written in cql-rb, but I ran the test
using astyana
Hi All,
I found a significant performance problem when using composite primary key,
"wide" row and BATCH.
Ideally, I would like to have following structure:
CREATE TABLE bar1 (
some_id bigint,
some_type text,
some_value int,
some_data text
