[ https://issues.apache.org/jira/browse/CASSANDRA-6146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13932326#comment-13932326 ]
Mikhail Stepura commented on CASSANDRA-6146: -------------------------------------------- Thanks [~benedict] bq. The installation instructions aren't as obvious as they could be. That can be fixed. bq. There is no support for prepared statements. That's true. But I created the plugin merely as a proof of concept, so that can be implemented bq. If I simply tweak the example write plan, and have it run > 10k samples per thread, it pretty much immediately exhausts C* of its available file handles I've just run 100 threads with 100000 samples on my laptop against 1 node CCM cluster with 2.0.x, and everything worked fine, (well, except expected {{SyntaxError}} when a random string was generated with {{'}} inside). What was your setup? bq. It would be good to have the examples unpack to one of JMeter's examples/templates directory. We can ship them as examples. But templates are different beasts. One has to register template in a {{user.properties}} file, which is shipped with JMeter. We can create a templates for sure, but user will have to register them manually bq. Also, once I opened the error log it was completely empty (until I tried running again with it open, at which point it starts filling up with errors) That's the way JMeter works. All those errors will be available in {{jmeter.log}} https://jmeter.apache.org/usermanual/get-started.html#logging Or user can use components like http://jmeter.apache.org/usermanual/component_reference.html#Save_Responses_to_a_file. I agree that one has to get used to Jmeter, but once it's done, the tool will be very useful. > CQL-native stress > ----------------- > > Key: CASSANDRA-6146 > URL: https://issues.apache.org/jira/browse/CASSANDRA-6146 > Project: Cassandra > Issue Type: New Feature > Components: Tools > Reporter: Jonathan Ellis > Fix For: 2.1 beta2 > > > The existing CQL "support" in stress is not worth discussing. We need to > start over, and we might as well kill two birds with one stone and move to > the native protocol while we're at it. -- This message was sent by Atlassian JIRA (v6.2#6252)