I’m not sure about Datastax’s official stance but using the SSD backed
instances (ed. i2.2xl, c3.4xl etc) outperform the m2.2xl greatly. Also, since
Datastax is pro-ssd, I doubt they would still recommend to stay on magnetic
disks.
That said, I have benchmarked all the way up to the c3.8xl inst
The last guidance I heard from DataStax was to use m2.2xlarge's on AWS and
put data on the ephemeral drivehave they changed this guidance?
Brian
On Tue, Aug 19, 2014 at 9:41 AM, Oleg Dulin wrote:
> Distinguished Colleagues:
>
> Our current Cassandra cluster on AWS looks like this:
>
> 3 no
Distinguished Colleagues:
Our current Cassandra cluster on AWS looks like this:
3 nodes in N. Virginia, one per zone.
RF=3
Each node is a c3.4xlarge with 2x160G SSDs in RAID-0 (~300 Gig SSD on
each node). Works great, I find it the most optimal configuration for a
Cassandra node.
But the ti
