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
 brian.m.j.fitzpatrick@gmail.com designates 209.85.215.172 as permitted
 sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:sender:date:x-google-sender-auth:message-id:subject
         :from:to:content-type;
        b=BxL/Q1gn40ppnz8MYzmDIdfrKHUdBCLttX/c8C//jJDlATs5lpHcu4Kqxulqe2ZAi9
         5FIM0Cxl6W95bsZ5wq7mf9KiJH81njspDoyikjNC/CaReecYyuxD0TfG9pd3bWo+3BBG
         c2bpskN4rcJIic6xhqkhvd6+aoV8XeNQz9uoI=
MIME-Version: 1.0
Sender: brian.m.j.fitzpatrick@gmail.com
Date: Wed, 23 Mar 2011 10:04:21 -0500
Message-ID: <AANLkTi=dgcqqF5YQ_rPfyc1q10AesX_tJfvNrJJUHW-V@mail.gmail.com>
Subject: Sizing a Cassandra cluster
From: Brian Fitzpatrick <brian.fitzpatrick@acm.org>
To: user@cassandra.apache.org
Content-Type: text/plain; charset=ISO-8859-1

I'm going through the process of specing out the hardware for a
Cassandra cluster. The relevant specs:

- Support 460 operations/sec (50/50 read/write workload). Row size
ranges from 4 to 8K.
- Support 29 million objects for the first year
- Support 365 GB storage for the first year, based on Cassandra tests
(data + index + overhead * replication factor of 3)

I'm looking for advice on the node size for this cluster, recommended
RAM per node, and whether RF=3 seems to be a good choice for general
availability and resistance to failure.

I've looked at the YCSB benchmark paper and through the archives of
this email list looking for pointers.  I haven't found any general
guidelines on recommended cluster size to support X operations/sec
with Y data size at RF factor of Z, that I could extrapolate from.

Any and all recommendations appreciated.

Thanks,
Brian