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: ec2 setup recommendations. http://wiki.apache.org/cassandra/CassandraHardware?action=diff&rev1=16&rev2=17 -------------------------------------------------- On ext2/ext3 the maximum file size is 2TB, even on a 64 bit kernel. On ext4 that goes up to 16TB. Since Cassandra can use almost half your disk space on a single file, if you are raiding large disks together you may want to use XFS instead, particularly if you are using a 32-bit kernel. XFS file size limits are 16TB max on a 32 bit kernel, and basically unlimited on 64 bit. === Cloud === - Several heavy users of Cassandra deploy in the cloud, e.g. CloudKick on Rackspace Cloud Servers and SimpleGeo on Amazon EC2. The general consensus in the community seems to be that Rackspace's VMs offer better performance for Cassandra because of CPU bursting, raided local disks, and separate public/private network interfaces. + 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. +
