cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pavel Yaskevich (JIRA)" <j...@apache.org>
Subject [jira] Updated: (CASSANDRA-1453) stress.java
Date Thu, 23 Dec 2010 14:26:03 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-1453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Pavel Yaskevich updated CASSANDRA-1453:
---------------------------------------

    Attachment: stress-v2.patch

.gitignore and @author tags removed. -server and -XX:CompileThreshold=1 added to ./bin/stress

I can add --warm-up option to the system which will run required action (insert, read etc.)
with given by user parameters before measuring performance and then run actual tests, this
is only way to perform warm-up I see here. Any other ideas?

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


Mime
View raw message