Ah excellent, thanks for clarifying!
On Tue, Aug 19, 2014 at 11:16 AM, Benedict Elliott Smith <belliottsm...@datastax.com> wrote: > The stress tool will work against any version of Cassandra, it's only > released alongside for ease of deployment. You can safely use the tool from > pre-release versions. > > > On Tue, Aug 19, 2014 at 11:03 PM, Clint Kelly <clint.ke...@gmail.com> wrote: >> >> Thanks for the update, Benedict. We are still using 2.0.9 >> unfortunately. :/ I will keep that in mind for when we upgrade. >> >> On Tue, Aug 19, 2014 at 10:51 AM, Benedict Elliott Smith >> <belliottsm...@datastax.com> wrote: >> > The stress tool in 2.1 also now supports clustering columns: >> > >> > http://www.datastax.com/dev/blog/improved-cassandra-2-1-stress-tool-benchmark-any-schema >> > >> > There are however some features up for revision before release in order >> > to >> > help generate realistic workloads. See >> > https://issues.apache.org/jira/browse/CASSANDRA-7519 for details. >> > >> > >> > On Tue, Aug 19, 2014 at 10:46 PM, Clint Kelly <clint.ke...@gmail.com> >> > wrote: >> >> >> >> Hi Mikail, >> >> >> >> This plugin looks great! I have actually been using JMeter + a custom >> >> REST endpoint driving Cassandra. It would be great to compare the >> >> results I got from that against the pure JMeter + Cassandra (to >> >> evaluate the REST endpoint's performance). >> >> >> >> Thanks! I'll check this out. >> >> >> >> Best regards, >> >> Clint >> >> >> >> >> >> On Tue, Aug 19, 2014 at 1:38 AM, Mikhail Stepura >> >> <mikhail.step...@outlook.com> wrote: >> >> > Are you interested in cassandra-stress in particular? Or in any tool >> >> > which >> >> > will allow you to stress test your schema? >> >> > I believe Apache Jmeter + CQL plugin may be useful in the latter >> >> > case. >> >> > >> >> > https://github.com/Mishail/CqlJmeter >> >> > >> >> > -M >> >> > >> >> > >> >> > >> >> > On 8/17/14 12:26, Clint Kelly wrote: >> >> >> >> >> >> Hi all, >> >> >> >> >> >> Is there a way to use the cassandra-stress tool with clustering >> >> >> columns? >> >> >> >> >> >> I am trying to figure out whether an application that I'm running on >> >> >> is slow because of my application logic, C* data model, or >> >> >> underlying >> >> >> C* setup (e.g., I need more nodes or to tune some parameters). >> >> >> >> >> >> My application uses tables with several clustering columns and a >> >> >> couple of additional indices and it is running quite slowly under a >> >> >> heavy write load. I think that the problem is my data model (and >> >> >> therefore table layout), but I'd like to confirm by replicating the >> >> >> problem with cassandra-stress. >> >> >> >> >> >> I don't see any option for using clustering columns or secondary >> >> >> indices, but I wanted to check before diving into the code and >> >> >> trying >> >> >> to add this functionality. >> >> >> >> >> >> Thanks! >> >> >> >> >> >> Best regards, >> >> >> Clint >> >> >> >> >> > >> > >> > > >
