Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (nike.apache.org: domain of rakeshxp@gmail.com designates
 209.85.221.192 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:from:date:message-id:subject:to:content-type;
        b=HIf+8y3SYMjpxEG1CSTZDVyh3fu04mb571+rjSSYV9qaaxsXckw8op6PWHkaIkvFfx
         N35klBL686sk3Yqqlt6KSZiejRPOeEmzvAgwlDrhX//dJ/8qFOhlVL+ztha50Nl4Qs5J
         KJK28FW+m/3HFoj/cUeJyo37DnCYLaM0lrQgQ=
MIME-Version: 1.0
From: Rakesh Rajan <rakeshxp@gmail.com>
Date: Sat, 1 May 2010 17:04:31 +0530
Message-ID: <y2ka94315c71005010434j34958699m3a9a5ec8e30cadd4@mail.gmail.com>
Subject: Design Query
To: user@cassandra.apache.org
Content-Type: multipart/alternative; boundary=0016364ecbf276fff6048586bf62

--0016364ecbf276fff6048586bf62
Content-Type: text/plain; charset=ISO-8859-1

I am evaluating cassandra to implement activity streams. We currently have
over 1000000 feeds with total entries exceeding 320000000 implemented using
redis ( ~320 entries / feed). Would like hear from the community on how to
use cassandra to solve the following cases:

   1. Ability to fetch entries by applying a few filters ( like show me only
   likes from a given user). This would include range query to support
   pagination. So this would mean indices on a few columns like the feed id,
   feed type etc.
   2. We have around 3 machines with 4GB RAM for this purpose and thinking
   of having replication factor 2. Would 4GB * 3 be enough for cassandra for
   this kind of data? I read that cassandra does not keep all the data in
   memory but want to be sure that we have the right server config to handle
   this data using cassandra.

Thanks,
Rakesh

--0016364ecbf276fff6048586bf62
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div>I am evaluating cassandra to implement activity streams. We currently =
have over 1000000 feeds with total entries exceeding 320000000 implemented =
using redis ( ~320 entries / feed). Would like hear from the community on h=
ow to use cassandra to solve the following cases:</div>

<div><ol><li>Ability to fetch entries by applying a few filters ( like show=
 me only likes from a given user). This would include range query to suppor=
t pagination. So this would mean indices on a few columns like the feed id,=
 feed type etc.</li>

<li>We have around 3 machines with 4GB RAM for this purpose and thinking of=
 having replication factor 2. Would 4GB * 3 be enough for cassandra for thi=
s kind of data? I read that cassandra does not keep all the data in memory =
but want to be sure that we have the right server config to handle this dat=
a using cassandra.</li>

</ol></div><div>Thanks,</div><div>Rakesh=A0</div>

--0016364ecbf276fff6048586bf62--