Do you think having SAS disks will give better performance?
On Sat, Mar 6, 2010 at 5:47 PM, Jonathan Ellis wrote:
> I think http://wiki.apache.org/cassandra/CassandraHardware answers
> most of your questions.
>
> If possible, it's definitely useful to try out a small fraction of
> your anticipate
So, do you think it will be problematic on a large scale? If yes is
it configurable in 0.6?
On Sat, Mar 6, 2010 at 6:19 PM, Avinash Lakshman
wrote:
> We have observed this. But in practice it doesn't cause any deleterious
> effects. IMHO detecting false failures of nodes is the most dangerous th
basics.html
>
> otherwise there's something wrong w/ your vm (?), disk i/o doesn't
> block incoming writes in cassandra
>
> On Thu, Feb 25, 2010 at 8:49 AM, Boris Shulman wrote:
>> I don't think it is gc related issue. There is no correlation between
>> gc tim
> otherwise there's something wrong w/ your vm (?), disk i/o doesn't
> block incoming writes in cassandra
>
> On Thu, Feb 25, 2010 at 8:49 AM, Boris Shulman wrote:
>> I don't think it is gc related issue. There is no correlation between
>> gc times and the f
r how to modify
> jvm options) for a correlation.
>
> On Thu, Feb 25, 2010 at 8:09 AM, Boris Shulman wrote:
>> In these tests I perform only write operations, no reads.
>>
>> On Thu, Feb 25, 2010 at 4:07 PM, Jonathan Ellis wrote:
>>> The only kind of "freeze&q
e RAM, or give less to the JVM so the OS can use more
> for buffer cache.
>
> On Thu, Feb 25, 2010 at 8:01 AM, Boris Shulman wrote:
>> In my case the cassandra node freezes while memtable flush operation
>> is performed or compactation operation is performed. How can I
>>
In my case the cassandra node freezes while memtable flush operation
is performed or compactation operation is performed. How can I
optimize the cassandra configuration in order to avoid this behavior?
I've tried both using large memtable size (1G) and small (128M) but in
every case I have some sor
Hello, I'm running some benchmarks on 2 cassandra nodes each running
on 8 cores machine with 16G RAM, 10G for Java heap. I've noticed that
during benchmarks with numerous writes cassandra just freeze for
several minutes (in those benchmarks I'm writing batches of 10 columns
with 1K data each for ev
