incubator-cassandra-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vegard Berget" <>
Subject Re: cassandra vs. mongodb quick question
Date Mon, 18 Feb 2013 09:08:41 GMT

	Just out of curiosity :

	When using compression, does this affect this one way or another?
 Is 300G (compressed) SSTable size, or total size of data?   

----- Original Message -----
Sent:Mon, 18 Feb 2013 08:41:25 +1300
Subject:Re: cassandra vs. mongodb quick question

 If you have spinning disk and 1G networking and no virtual nodes, I
would still say 300G to 500G is a soft limit. 
 If you are using virtual nodes, SSD, JBOD disk configuration or
faster networking you may go higher.  
 The limiting factors are the time it take to repair, the time it
takes to replace a node, the memory considerations for 100's of
millions of rows. If you the performance of those operations is
acceptable to you, then go crazy.  
  ----------------- Aaron Morton Freelance Cassandra Developer New
 @aaronmorton [1]   
 On 16/02/2013, at 9:05 AM, "Hiller, Dean"  wrote: 
So I found out mongodb varies their node size from 1T to 42T per node
depending on the profile.  So if I was going to be writing a lot but
rarely changing rows, could I also use cassandra with a per node size
of +20T or is that not advisable?




View raw message