[
https://issues.apache.org/jira/browse/CASSANDRA-6737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15080952#comment-15080952
]
Sylvain Lebresne commented on CASSANDRA-6737:
---------------------------------------------
bq. Would you say there's any limitation/recommendation regarding the number of
statements contained in a single partition batch (or the summarized size in kb)?
A single partition batch is internally a single mutation, so unless I've missed
some recent changes to the commit log, you're hard-limited by the size of a
commit log segment, and believe by default we actually limit that to half of
the segment, so 16MB (see {{max_mutation_size_in_kb}} in the yaml).
Now, I'd really appreciate it if you could use the mailing list for such
question as it is a more appropriate venue (especially since the question is
barely related to the original ticket).
> A batch statements on a single partition should not create a new CF object
> for each update
> ------------------------------------------------------------------------------------------
>
> Key: CASSANDRA-6737
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6737
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Sylvain Lebresne
> Assignee: Sylvain Lebresne
> Labels: performance
> Fix For: 2.0.6
>
> Attachments: 6737.2.patch, 6737.txt
>
>
> BatchStatement creates a new ColumnFamily object (as well as a new
> RowMutation object) for every update in the batch, even if all those update
> are actually on the same partition. This is particularly inefficient when
> bulkloading data into a single partition (which is not all that uncommon).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
