Not using a commit log at all isn't something I had considered. We may very well be able to do that for our application. Thanks.
On Sat, Nov 16, 2013 at 6:17 PM, Tupshin Harper <tups...@tupshin.com> wrote: > It's conceivable that one of the faster USB 3.0 sticks would be sufficient > for this. I wouldn't exactly call it an "enterprise" configuration, but it's > worth considering. Keep in mind that if you are comfortable using your RF > for durability, you can turn off durable_writes on your keyspace and not > write to the commitlog at all. > > > > On Sat, Nov 16, 2013 at 11:05 AM, Philippe <watche...@gmail.com> wrote: >> >> Hi david, we tried it two years ago and the performance of the USB stick >> was so dismal we stopped. >> Cheers >> >> Le 16 nov. 2013 15:13, "David Tinker" <david.tin...@gmail.com> a écrit : >> >>> Our hosting provider has a cost effective server with 2 x 4TB disks >>> with a 16G (or 64G) USB thumb drive option. Would it make sense to put >>> the Cassandra commit log on the USB thumb disk and use RAID0 to use >>> both 4TB disks for data (and Ubuntu 12.04)? >>> >>> Anyone know how long USB flash disks last when use for a write heavy >>> workload like this? >>> >>> Please tell me if this is a really bad idea. >>> >>> Our alternative is to use one 4TB disk for commit log and one for >>> data. Of course this will give us only half the space. >>> >>> Thanks >>> David > > -- http://qdb.io/ Persistent Message Queues With Replay and #RabbitMQ Integration
