Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
MIME-Version: 1.0
Date: Tue, 16 Jun 2015 15:08:45 +0530
Message-ID: 
 <CALAVqMuxTLx3W2-1qjKYCoYA_nvwK3edzCZQpeV6QNQ5dgCwRw@mail.gmail.com>
Subject: Tuning Cassandra 2.1 for High Writes and Immediate Reads
From: Pracheer Agarwal <pracheeragarwal@gmail.com>
To: user@cassandra.apache.org
Content-Type: multipart/alternative; boundary=001a11473b123be5eb05189f57ca

--001a11473b123be5eb05189f57ca
Content-Type: text/plain; charset=UTF-8

Hi,

We are evaluating Cassandra 2.1 for our new production system. The
following are the requirements:

1. 15K writes/sec with 5 KB blob in a single column of a column family,
2. This is followed by immediate Reads by multiple consumer threads, the
read requires us to return entire Row and not only the recently updated
column.
3. Around 1B unique keys.

So I am assuming for the reads the data can be fetched from both Memtable
(if it is not flushed) and Key-cache. (Row-cache is disabled)

How can we optimize for higher Read throughput at the cost of Writes?

Machine configuration, 10 Node cluster.

   - 24 core/machine
   - 64 GB RAM
   - 2TB*5 HDD per machine
   - 10G NIC


Till now, for optimization we have done the following:
1. We have provided 4G keycache.
2. Created parition-key and clustering key in such a way that, for every
new event a new cell is created, we never update a record.
3. No light-weight transactions
4. ReplicationFactor 3
5. Write quorum 2, Read quorum 2

How can we further optimize for the write/read patterns explained above?

Thanks,
Pracheer

--001a11473b123be5eb05189f57ca
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi,<div><br></div><div>We are evaluating Cassandra 2.1 for=
 our new production system. The following are the requirements:</div><div><=
br></div><div>1. 15K writes/sec with 5 KB blob in a single column of a colu=
mn family,=C2=A0</div><div>2. This is followed by immediate Reads by multip=
le consumer threads, the read requires us to return entire Row and not only=
 the recently updated column.</div><div>3. Around 1B unique keys.</div><div=
><br></div><div>So I am assuming for the reads the data can be fetched from=
 both Memtable (if it is not flushed) and Key-cache. (Row-cache is disabled=
)=C2=A0</div><div><br></div><div>How can we optimize for higher Read throug=
hput at the cost of Writes?</div><div><br></div><div>Machine configuration,=
 10 Node cluster.</div><div><ul><li>24 core/machine</li><li>64 GB RAM</li><=
li>2TB*5 HDD per machine</li><li>10G NIC=C2=A0</li></ul></div><div><br></di=
v><div>Till now, for optimization we have done the following:</div><div>1. =
We have provided 4G keycache.</div><div>2. Created parition-key and cluster=
ing key in such a way that, for every new event a new cell is created, we n=
ever update a record.</div><div>3. No light-weight transactions</div><div>4=
. ReplicationFactor 3</div><div>5. Write quorum 2, Read quorum 2</div><div>=
<br></div><div>How can we further optimize for the write/read patterns expl=
ained above?</div><div><br></div><div>Thanks,</div><div>Pracheer</div></div=
>

--001a11473b123be5eb05189f57ca--