[ 
https://issues.apache.org/jira/browse/CASSANDRA-9302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15049403#comment-15049403
 ] 

Adam Holmberg commented on CASSANDRA-9302:
------------------------------------------

This is looking good. To respond to a few of your comments:

bq. Perhaps I'm doing something wrong but a single session created with the 
code below returns lots of timeouts 
The snippet you show there is still using WhiteList instead of DCAware for the 
inner policy.

bq. I could not get it to work (the callbacks where no longer called, perhaps 
the self parameter?).
Not a big deal either way. If you're interested the cassandra.concurrent module 
shows this working with bound methods: 
https://github.com/datastax/python-driver/blob/3.0.0/cassandra/concurrent.py#L127-L129

bq.  just to be sure I compared the performance of strings vs prepared 
statements again today and I encountered lots of timeouts
This is a little surprising to me, but I trust your empirical observations and 
don't want to make a science project out of it. Maybe we're bottlenecking on 
server resources instead of per-python CPU. I must admit I haven't completely 
characterized workloads that are better-suited for built strings -- I've just 
seen it in the wild.

> 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)

Reply via email to