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 6D47E1066B for ; Mon, 12 Aug 2013 17:23:10 +0000 (UTC) Received: (qmail 52909 invoked by uid 500); 12 Aug 2013 17:23:07 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 52533 invoked by uid 500); 12 Aug 2013 17:23:07 -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 52525 invoked by uid 99); 12 Aug 2013 17:23:06 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 12 Aug 2013 17:23:06 +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 paulingalls@gmail.com designates 209.85.160.52 as permitted sender) Received: from [209.85.160.52] (HELO mail-pb0-f52.google.com) (209.85.160.52) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 12 Aug 2013 17:23:00 +0000 Received: by mail-pb0-f52.google.com with SMTP id wz12so6918273pbc.39 for ; Mon, 12 Aug 2013 10:22:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:content-type:subject:message-id:date:to:mime-version; bh=nEkGZ4YRWimAgGMDYJpqWgvcNhM5Ci76bJBS56Pp2fE=; b=uWMYis7syTN+mhpKetan4N64AhRuR1VYyCeeU+5lVsrJV/uwI3ud0r8RjHAY/Lm1m1 HJuxQ1SsNZIUNWNgBJ3emdzunS8pzjo0nCn07fHAr2NxfepR8foFwiZEyhwerypBm8T4 8rwOflHZON3pZyuXEKB44GNmipACM7gZhNCzDECt6bKKa+wfOlCMUPHlSRu9+4KQHUan gt4/IA7kKxLEnOfdMg+b16DD5FfM7jvonGUD/VxXjotl2ZUnHkLoS3GA4WP1SGODo0/F rwZqbJGIOcub62UHrZfSkK/GgsjPeDiTyuLPT9ImQMv3SHCs8OidLxSn9nzRQ0fARm6V KLtg== X-Received: by 10.66.187.34 with SMTP id fp2mr146494pac.12.1376328160005; Mon, 12 Aug 2013 10:22:40 -0700 (PDT) Received: from [192.168.15.76] (184-78-184-52.war.clearwire-wmx.net. [184.78.184.52]) by mx.google.com with ESMTPSA id s5sm38453771pbo.38.2013.08.12.10.22.38 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 12 Aug 2013 10:22:39 -0700 (PDT) From: Paul Ingalls Content-Type: multipart/alternative; boundary="Apple-Mail=_B251A6CA-4F33-4F4A-AABD-E2B7E69D29BB" Subject: understanding memory footprint Message-Id: Date: Mon, 12 Aug 2013 10:22:36 -0700 To: "user@cassandra.apache.org" Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\)) X-Mailer: Apple Mail (2.1508) X-Virus-Checked: Checked by ClamAV on apache.org --Apple-Mail=_B251A6CA-4F33-4F4A-AABD-E2B7E69D29BB Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=windows-1252 I'm trying to get a handle on how newer cassandra handles memory. Most = of what I am seeing via google, on the wiki etc. appears old. For = example, this wiki article appears out of date relative to post 1.0: http://wiki.apache.org/cassandra/MemtableThresholds specifically this is the section I'm looking at: For a rough rule of thumb, Cassandra's internal datastructures will = require about memtable_throughput_in_mb * 3 * number of hot CFs + 1G + = internal caches. is this still true? I thought memtable_throughput_in_mb is deprecated. = Is there any equivalent calculation/rule of thumb for cassandra post = 1.0? At the core, my question really is: "Does the number of column families still significantly impact the = memory footprint? If so, what is the incremental cost of a column = family/table?" and the available docs aren't helping me answer it=85 Thanks! Paul= --Apple-Mail=_B251A6CA-4F33-4F4A-AABD-E2B7E69D29BB Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=windows-1252 I'm = trying to get a handle on how newer cassandra handles memory.  Most = of what I am seeing via google, on the wiki etc. appears old.  For = example, this wiki article appears out of date relative to post = 1.0:


specif= ically this is the section I'm looking = at:

 For a rough rule of thumb, = Cassandra's internal datastructures will require = about memtable_throughput_in_mb * 3 * number of hot CFs + 1G + = internal caches.

is this still true?  I thought = memtable_throughput_in_mb is deprecated.  Is there any equivalent = calculation/rule of thumb for cassandra post = 1.0?

At the core, my question really = is:

"Does the number of column families still = significantly impact the memory footprint? If so, what is the = incremental cost of a column family/table?"

and = the available docs aren't helping me answer = it=85

Thanks!

Paul
= = --Apple-Mail=_B251A6CA-4F33-4F4A-AABD-E2B7E69D29BB--