@cassandra.apache.org, Vegard Berget
p...@fantasista.nomailto:p...@fantasista.no
Subject: Re: cassandra vs. mongodb quick question
My experience is repair of 300GB compressed data takes longer than 300GB of
uncompressed, but I cannot point to an exact number. Calculating the
differences is mostly CPU
but the data
is still good on the drives, it would just mean bringing up the node using the
same storage ? would this not be fast…?
From: aaron morton [mailto:aa...@thelastpickle.com]
Sent: 21 February 2013 11:46
To: user@cassandra.apache.org
Subject: Re: cassandra vs. mongodb quick question
Date: Monday, February 18, 2013 1:39 PM
To: user@cassandra.apache.orgmailto:user@cassandra.apache.org
user@cassandra.apache.orgmailto:user@cassandra.apache.org, Vegard Berget
p...@fantasista.nomailto:p...@fantasista.no
Subject: Re: cassandra vs. mongodb quick question
My experience is repair
@cassandra.apache.orgmailto:user@cassandra.apache.org
Date: Wednesday, February 20, 2013 1:04 PM
To: user@cassandra.apache.orgmailto:user@cassandra.apache.org
user@cassandra.apache.orgmailto:user@cassandra.apache.org
Subject: Re: cassandra vs. mongodb quick question(good additional info)
This calculation
of data?
.vegard,
- Original Message -
From:
user@cassandra.apache.orgmailto:user@cassandra.apache.org
To:
user@cassandra.apache.orgmailto:user@cassandra.apache.org
Cc:
Sent:
Mon, 18 Feb 2013 08:41:25 +1300
Subject:
Re: cassandra vs. mongodb quick question
If you have spinning
@cassandra.apache.org
user@cassandra.apache.orgmailto:user@cassandra.apache.org, Vegard Berget
p...@fantasista.nomailto:p...@fantasista.no
Subject: Re: cassandra vs. mongodb quick question
My experience is repair of 300GB compressed data takes longer than 300GB of
uncompressed, but I cannot point
, 2013 7:02:56 AM
Subject: Re: cassandra vs. mongodb quick question(good additional info)
The 40 TB use case you heard about is probably one 40TB mysql machine
that someone migrated to mongo so it would be web scale Cassandra is
NOT good with drives that big, get a blade center or a high density
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
-
From:
user@cassandra.apache.org
To:
user@cassandra.apache.org
Cc:
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
@cassandra.apache.orgmailto:user@cassandra.apache.org, Vegard Berget
p...@fantasista.nomailto:p...@fantasista.no
Subject: Re: cassandra vs. mongodb quick question
My experience is repair of 300GB compressed data takes longer than 300GB of
uncompressed, but I cannot point to an exact number. Calculating
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
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?
Thanks,
Dean
12 matches
Mail list logo
