Actually, many SSD drives show much better performance for sequential write
then random writes, so you may benefit from a separate drive for commit
logs.
On Mon, Sep 23, 2013 at 11:21 AM, Robert Coli wrote:
> On Sun, Sep 22, 2013 at 4:02 PM, Shahryar Sedghi wrote:
>
>> This my first SSD experi
On Sun, Sep 22, 2013 at 4:02 PM, Shahryar Sedghi wrote:
> This my first SSD experience. With normal disks we separate commit log
> from data. We have 2 SSDs dedicated to Cassandra I was wondering if we
> gain a better performance if we put commit log in one and data in
> another, or just use
Having commit log and data directory under one SSD works well. Though it
depends a lot on the use case. I would measure the Disk utilization and see
whether it can be on one. For most of the cases, it will work fine on one
SSD.
On Sun, Sep 22, 2013 at 4:02 PM, Shahryar Sedghi wrote:
> This my f
This my first SSD experience. With normal disks we separate commit log
from data. We have 2 SSDs dedicated to Cassandra I was wondering if we
gain a better performance if we put commit log in one and data in
another, or just use raid 0 to have both SSDs combined.
Thanks in Advance
Shahryar
