Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Message-ID: <14632933.9201293183526647.JavaMail.jira@thor>
Date: Fri, 24 Dec 2010 04:38:46 -0500 (EST)
From: "Pavel Yaskevich (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Subject: [jira] Commented: (CASSANDRA-1453) stress.java
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Pavel Yaskevich commented on CASSANDRA-1453:
--------------------------------------------

This confirm my hunch about wrong node selected for read, python has the same issue with randomly selected nodes as logic was ported from it, solution here is to set Consistency Level > ONE, only this makes sense here...

> stress.java
> -----------
>
>                 Key: CASSANDRA-1453
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-1453
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Tools
>            Reporter: Jonathan Ellis
>            Assignee: Pavel Yaskevich
>            Priority: Minor
>             Fix For: 0.7.1
>
>         Attachments: stress-v2.patch, stress.patch
>
>
> stress.py seems to scale poorly past a fairly small number of threads/processes.  (against a 3-node, RF=1 cluster, I got 3x as much throughput with 4 machines running stress.py -t 32, as running 1 with -t 128.  these were 8-core client machines, and -t 128 reported only 50% cpu used.)
> since we ship with the thrift java api pre-built, this would also mean not making people build thrift before using the stress test, which is at best a pain for newcomers and on Windows a major hurdle.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.