Sasha, You might also check out http://coreyhulen.org/category/cassandra/ for speed tests done by Corey Hulan on different disk configurations (both inside ec2 and on real hw).
If you write to the ephermeral storage on an EC2 instance, there is no additional cost for the data written. Mostly similarly with EBS. In EBS you pay for the disk size you allocate. There's a tiny additional charge for IO (currently $0.10 per 1M io requests). HTH, Dave Viner On Wed, Mar 9, 2011 at 8:48 AM, Sasha Dolgy <sdo...@gmail.com> wrote: > Hi Will, > > http://wiki.apache.org/cassandra/Operations#Backing_up_data > > <http://wiki.apache.org/cassandra/Operations#Backing_up_data>If the > snapshot is written to the ephemeral storage ... there isn't a cost. (i need > to confirm that) > > You can then move this to an S3 bucket with RDS if you want or full > 99.999999999% redundancy and have it available to developers > > This is what I had in my head.... > -sd > > > On Wed, Mar 9, 2011 at 5:39 PM, William Oberman > <ober...@civicscience.com>wrote: > >> I thought nodetool snapshot writes the snapshot locally, requiring 2x of >> expensive storage allocation 24x7 (vs. cheap storage allocation of a ebs >> snapshot). By that I mean EBS allocation is GB allocated per month costs at >> one rate, and EBS snapshots are delta compressed copies to S3. >> >> Can you point the snapshot to an external filesystem? >> >> will >> >>
