[ https://issues.apache.org/jira/browse/CASSANDRA-6146?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13931630#comment-13931630 ]
Benedict edited comment on CASSANDRA-6146 at 3/12/14 10:51 AM: --------------------------------------------------------------- Sorry for the glacial response on this [~mishail]. I've setup my JIRA search to include items awaiting my review so it shouldn't happen again. First impressions: # The installation instructions aren't as obvious as they could be. I tried a variety of fairly stupid things because it didn't make it clear (to me) exactly which releases I should be downloading/unpacking where. Would be good to state unambiguously that you should download the CqlJMeter binary release, and a JMeter binary release, and that tar -xjf \{CqlJMeter.tgz\} -C \{Unpacked JMeter Root Directory\} will get everything working. # There is no support for prepared statements. # 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. Now, by default on my system the number of available file handles is not very many, but something is going wrong if I can exhaust them with only the default 10 threads configured (cassandra-stress does not exhaust them with hundreds of threads). # It would be good to have the examples unpack to one of JMeter's examples/templates directory. You see a mongodb template in there straight away (bundled), when you click "open", so it would be nice to have Cassandra there without having to go hunting somewhere else for it. 2 and 3 are pretty much show stoppers for me. Once they're sorted, it might be worth trying to package it with JMeter, since mongodb is. Personally I also don't find JMeter to be an easy or intuitive way to get running quickly with stress testing, but that's a completely separate matter, and your bundled plan does make it much more straight forward than it would otherwise be. It looks like it is quite powerful and certainly very expressive, so for serious/complex stress testing and benchmarking it looks like it could be a great tool. was (Author: benedict): Sorry for the glacial response on this [~mishail]. I've setup my JIRA search to include items awaiting my review so it shouldn't happen again. First impressions: 1) The installation instructions aren't as obvious as they could be. I tried a variety of fairly stupid things because it didn't make it clear (to me) exactly which releases I should be downloading/unpacking where. Would be good to state unambiguously that you should download the CqlJMeter binary release, and a JMeter binary release, and that tar -xjf \{CqlJMeter.tgz\} -C \{Unpacked JMeter Root Directory\} will get everything working. 2) There is no support for prepared statements. 3) 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. Now, by default on my system the number of available file handles is not very many, but something is going wrong if I can exhaust them with only the default 10 threads configured (cassandra-stress does not exhaust them with hundreds of threads). 4) It would be good to have the examples unpack to one of JMeter's examples/templates directory. You see a mongodb template in there straight away (bundled), when you click "open", so it would be nice to have Cassandra there without having to go hunting somewhere else for it. 2 and 3 are pretty much show stoppers for me. Once they're sorted, it might be worth trying to package it with JMeter, since mongodb is. Personally I also don't find JMeter to be an easy or intuitive way to get running quickly with stress testing, but that's a completely separate matter, and your bundled plan does make it much more straight forward than it would otherwise be. It looks like it is quite powerful and certainly very expressive, so for serious/complex stress testing and benchmarking it looks like it could be a great tool. > 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)