Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (athena.apache.org: domain of shulmanb@gmail.com designates
 74.125.82.172 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=r7ytKETlkK/tfIbdgeYn42gcA6+Qt617hM1zl0ggWXj2OxI9XjY2mDifi0QtXh4cxd
         mxVZvgiKAM3QLEZOlFw5tyN53p0V8q5Xdfh+Gey75fXEuDScfZr0S39idqs8tWHRWeBg
         2y6v+w7voEoQ8lqnoLrNe4dDhX5Oef8/NJ63Y=
MIME-Version: 1.0
In-Reply-To: <4C0D124D.8030006@strands.com>
References: <4C0D124D.8030006@strands.com>
Date: Wed, 9 Jun 2010 12:59:00 +0300
Message-ID: <AANLkTind0qIShRXrDUqc9aIzPGAF-2MAecbDtyPNXU8X@mail.gmail.com>
Subject: Re: Cassandra on flash storage
From: Boris Shulman <shulmanb@gmail.com>
To: user@cassandra.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Using SSD for a commitlog device can bost performance while using
cassandra in a batch mode for fsync operations. From my experience ta
write operation can be 10 times faster when usding SSD for commitlog.

On Mon, Jun 7, 2010 at 6:37 PM, H=E9ctor Izquierdo <izquierdo@strands.com> =
wrote:
> Hi everyone.
>
> I wanted to know if anybody has had any experience with cassandra on flas=
h
> storage. At work we have a cluster of 6 machines running Tokyotyrant on
> flash-io drives (320GB) each, but performance is not what we expected, an=
d
> we'are having some issues with replication and availability. It's also ha=
rd
> to manage, and adding/removing nodes is pure hell.
>
> We can't afford test hardware with flash storage right now, so could
> somebody share his experience?
>
> Thank you very much
>
> H=E9ctor Izquierdo
>