cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Cassandra Wiki] Update of "CassandraHardware" by JonathanEllis
Date Wed, 09 Mar 2011 20:56:46 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Cassandra Wiki" for change notification.

The "CassandraHardware" page has been changed by JonathanEllis.
The comment on this change is: link eonnen's EBS explanation.
http://wiki.apache.org/cassandra/CassandraHardware?action=diff&rev1=17&rev2=18

--------------------------------------------------

  === Cloud ===
  Several heavy users of Cassandra deploy in the cloud, e.g. CloudKick on Rackspace Cloud
Servers and SimpleGeo on Amazon EC2.
  
- On EC2, the best practice is to use L or XL instances with local storage.  I/o performance
is proportionately much worse on S and M sizes, and EBS essentially doubles your dependence
on the already-overcrowded EC2 network (https://www.cloudkick.com/blog/2010/jan/12/visual-ec2-latency/),
so you want to avoid that.  Put the Cassandra commitlog on the root volume, and the data directory
on the raid0'd ephemeral disks.
+ On EC2, the best practice is to use L or XL instances with local storage.  I/o performance
is proportionately much worse on S and M sizes, and EBS is a bad fit for several reasons (see
[[http://www.mail-archive.com/user@cassandra.apache.org/msg11022.html|Erik Onnen's excellent
explanation]]).  Put the Cassandra commitlog on the root volume, and the data directory on
the raid0'd ephemeral disks.
  

Mime
View raw message