Return-Path: X-Original-To: apmail-cassandra-user-archive@www.apache.org Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id AE678D0EE for ; Thu, 8 Nov 2012 22:36:55 +0000 (UTC) Received: (qmail 51916 invoked by uid 500); 8 Nov 2012 22:36:53 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 51894 invoked by uid 500); 8 Nov 2012 22:36:53 -0000 Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@cassandra.apache.org Delivered-To: mailing list user@cassandra.apache.org Received: (qmail 51870 invoked by uid 99); 8 Nov 2012 22:36:53 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 08 Nov 2012 22:36:53 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of kohlisankalp@gmail.com designates 209.85.216.172 as permitted sender) Received: from [209.85.216.172] (HELO mail-qc0-f172.google.com) (209.85.216.172) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 08 Nov 2012 22:36:46 +0000 Received: by mail-qc0-f172.google.com with SMTP id b25so2441206qca.31 for ; Thu, 08 Nov 2012 14:36:26 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=CpigeODwwA3bWByqeO7pP1dOAaAmwcRjXLN2hJQ2BpY=; b=lmv5BgbH9QV4jo14Hm9CoE80lgEFQ/Rd8mIUeXN9qHGjPXUkVijFD8aBBC2hP3yjZj fOlU2YR9aTWMkJZmXa6Ppnqa+nsGOCPPmCKxJErKgpDGQw0elWdDxyq6rr2A++mIXRqa 3+9tVmlsnByLfg3iTVs5YzHLJSj3cMgLCAPyP/sm8ZzB/qz/NALHRufoW3iUm0tlCMNO XM4BVLtSAJM7eGxB6cAsoIBNh8vAM+gFvRqMENFpNHLcMu2a9qcrhF6lacEbLBNon/dj lDqToVMX8VOQIglKNSe57nhO0k0q5cFRtAY6KSPM5FD34+cm0wF6Q3Vk5qLUGeuutpXK A7oQ== Received: by 10.49.82.68 with SMTP id g4mr11960997qey.54.1352414185825; Thu, 08 Nov 2012 14:36:25 -0800 (PST) MIME-Version: 1.0 Received: by 10.49.96.168 with HTTP; Thu, 8 Nov 2012 14:36:05 -0800 (PST) In-Reply-To: References: From: sankalp kohli Date: Thu, 8 Nov 2012 14:36:05 -0800 Message-ID: Subject: Re: Multiple keyspaces vs Multiple CFs To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=047d7b5dbd5c22a60904ce037775 X-Virus-Checked: Checked by ClamAV on apache.org --047d7b5dbd5c22a60904ce037775 Content-Type: text/plain; charset=ISO-8859-1 Which connection pool are you talking about? On Thu, Nov 8, 2012 at 2:19 PM, Edward Capriolo wrote: > it is better to have one keyspace unless you need to replicate the > keyspaces differently. The main reason for this is that changing > keyspaces requires an RPC operation. Having 10 keyspaces would mean > having 10 connection pools. > > On Thu, Nov 8, 2012 at 4:59 PM, sankalp kohli > wrote: > > Is it better to have 10 Keyspaces with 10 CF in each keyspace. or 100 > > keyspaces with 1 CF each. > > I am talking in terms of memory footprint. > > Also I would be interested to know how much better one is over other. > > > > Thanks, > > Sankalp > --047d7b5dbd5c22a60904ce037775 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Which connection pool are you talking about?=A0
<= br>
On Thu, Nov 8, 2012 at 2:19 PM, Edward Ca= priolo <edlinuxguru@gmail.com> wrote:
it is better to have one keyspace unless you= need to replicate the
keyspaces differently. The main reason for this is that changing
keyspaces requires an RPC operation. Having 10 keyspaces would mean
having 10 connection pools.

On Thu, Nov 8, 2012 at 4:59 PM, sankalp kohli <kohlisankalp@gmail.com> wrote:
> Is it better to have 10 Keyspaces with 10 CF in each keyspace. or 100<= br> > keyspaces with 1 CF each.
> I am talking in terms of memory footprint.
> Also I would be interested to know how much better one is over other.<= br> >
> Thanks,
> Sankalp

--047d7b5dbd5c22a60904ce037775--