many BATCH inserts in to many?
With regard to a large number of records in a batch mutation there are
some potential issues.
Each row becomes a task in the write thread pool on each replica. If a
single client sends 1,000 rows in a mutation it will take time for the
(default) 32 threads
Sent: Sunday, January 13, 2013 7:57:56 PM
Subject: Re: How many BATCH inserts in to many?
With regard to a large number of records in a batch mutation there are
some potential issues.
Each row becomes a task in the write thread pool on each replica. If a
single client sends 1,000 rows
do not use cassandra for implementing queueing system with high
throughput. It does not scale because of tombstone management. Use
hornetQ, its amazingly fast broker but it has quite slow persistence if
you want to create queues significantly larger then your memory and use
selectors for
With regard to a large number of records in a batch mutation there are some
potential issues.
Each row becomes a task in the write thread pool on each replica. If a single
client sends 1,000 rows in a mutation it will take time for the (default) 32
threads in the write pool to work through
@cassandra.apache.org
Sent: Sunday, January 13, 2013 7:57:56 PM
Subject: Re: How many BATCH inserts in to many?
With regard to a large number of records in a batch mutation there are some
potential issues.
Each row becomes a task in the write thread pool on each replica. If a single
client sends 1,000 rows
Hello,
I have managed to insert up to 63k records without any problem. In certain
workloads I found that massive batch inserts perform way better than lots of
not-so-massive inserts. I guess it also depends on your setup. Just try it.
Alan Ristić alan.ris...@gmail.com escreveu:
Hi,
I'm
wauu! huh...em...wau - can't say anything else. Tnx for insight, it
certanly gives me some frame how batch is performing. Tnx a lot.
2013/1/12 Carlos Rolo c.r...@ocom.com
63k rec
Lp,
*Alan Ristić*
*m*: 040 423 688
Hi,
I'm implementing Facebook style notifications/activities (e.g your friend
liked this article) in our app. I considered message queue for this task
before exploring how BATCH insert in C* could perform. Could I leave Queue
altogether and just use batch insert? Is like...5000 insers too much
