[
https://issues.apache.org/jira/browse/CASSANDRA-6737?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15073752#comment-15073752
]
Martin Grotzke commented on CASSANDRA-6737:
-------------------------------------------
[~slebresne] 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)? Does a RowMutation for single partition batch statements become
more "expensive" if it contains more statements, e.g. does the heap pressure
grow with the number of contained statements?
(this question is related to my [comment in
CASSANDRA-6487|https://issues.apache.org/jira/browse/CASSANDRA-6487?focusedCommentId=15059781&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15059781])
> 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)
