[
https://issues.apache.org/jira/browse/CASSANDRA-9302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15058213#comment-15058213
]
Adam Holmberg commented on CASSANDRA-9302:
------------------------------------------
bq. We need to batch by replica rather than just by partition key as the scope
is much wider.
Right, I was forgetting about that optimization. I'm now surprised by this:
bq. I've repeated the tests today with pk batching rather than replica batching
and it shaved another 6 seconds.
Is this with a similar distribution of PKs? RF < N? Would it hold for a
non-local cluster where the round trip is not negligible?
Now looking at changes around ingest rate.
> Optimize cqlsh COPY FROM, part 3
> --------------------------------
>
> Key: CASSANDRA-9302
> URL: https://issues.apache.org/jira/browse/CASSANDRA-9302
> Project: Cassandra
> Issue Type: Improvement
> Components: Tools
> Reporter: Jonathan Ellis
> Assignee: Stefania
> Priority: Critical
> Fix For: 2.1.x
>
>
> We've had some discussion moving to Spark CSV import for bulk load in 3.x,
> but people need a good bulk load tool now. One option is to add a separate
> Java bulk load tool (CASSANDRA-9048), but if we can match that performance
> from cqlsh I would prefer to leave COPY FROM as the preferred option to which
> we point people, rather than adding more tools that need to be supported
> indefinitely.
> Previous work on COPY FROM optimization was done in CASSANDRA-7405 and
> CASSANDRA-8225.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
