my guess)
> Thanks,
> Dean
>
> From: , Nrel mailto:dean.hil...@nrel.gov>>
> Date: Tuesday, April 2, 2013 6:40 AM
> To: "user@cassandra.apache.org<mailto:user@cassandra.apache.org>"
> mailto:user@cassandra.apache.org>>
> Subject: Re: how to test our
ilto:aa...@thelastpickle.com>>
Reply-To: "user@cassandra.apache.org<mailto:user@cassandra.apache.org>"
mailto:user@cassandra.apache.org>>
Date: Monday, April 1, 2013 11:01 PM
To: "user@cassandra.apache.org<mailto:user@cassandra.apache.org>"
mailto:user
>>
Reply-To: "user@cassandra.apache.org<mailto:user@cassandra.apache.org>"
mailto:user@cassandra.apache.org>>
Date: Monday, April 1, 2013 11:01 PM
To: "user@cassandra.apache.org<mailto:user@cassandra.apache.org>"
mailto:user@cassandra.apache.org>>
Su
> If not, maybe I just generate the same 1,000,000 files on each machine, then
> randomly delete 1/2 the files and stream them from the other machine as
> writing those files would all be in random locations again forcing a much
> worse measurement of MB/sec I would think.
Not sure I understand
(we plan on running similar performance tests on cassandra but wanted to
understand the raw foot print first)…..
Someone in ops was doing a test transferring 1T of data from one node to
another. I had a huge concern I emailed him that this could end up being a
completely sequential write not t
