Thanks a ton, Juho.
The command was:
./stress.py -o read -t 50 -d $NODELIST -n 75000000 -k -i 2
I made a few minor modifications to stress.py to count errors instead of
logging them, and avoid the pointless try-catch on missing keys. (There are
also unrelated edits to restart long runs of inserts.)
My version is uploaded here:
http://gist.github.com/481966
--
David Schoonover
On Jul 19, 2010, at 4:26 PM, Juho Mäkinen wrote:
> I'm about to extend my two node cluster with four dedicated nodes and
> removing one of the old nodes, leaving a five node cluster. The
> cluster is in production, but I can spare it to do some stress testing
> in the meantime as I'm also interested about my cluster performance. I
> can't dedicate the cluster for the test, but the load at day time
> should be low enough not to screw with the end results too much. The
> results might come in within a few days as we'll get the nodes up -
> hopefully my tests will produce something meaningful data which can be
> applied to this issue.
>
> I haven't used stress.py yet, any tips on that? Could you, David, send
> me the stress.py command line which you used?
>
> - Juho Mäkinen
