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 0AAC911E24 for ; Tue, 9 Sep 2014 18:03:28 +0000 (UTC) Received: (qmail 77086 invoked by uid 500); 9 Sep 2014 18:03:22 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 77051 invoked by uid 500); 9 Sep 2014 18:03:22 -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 77041 invoked by uid 99); 9 Sep 2014 18:03:22 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Sep 2014 18:03:22 +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 (nike.apache.org: domain of oruchovets@gmail.com designates 209.85.213.180 as permitted sender) Received: from [209.85.213.180] (HELO mail-ig0-f180.google.com) (209.85.213.180) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Sep 2014 18:02:56 +0000 Received: by mail-ig0-f180.google.com with SMTP id hn18so4995572igb.13 for ; Tue, 09 Sep 2014 11:02:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=GzCwJCdR6ogTeiFoLhqdgJYw+XPMpMZhII1XmOwA4bU=; b=jq2pYr1Em7CEdpR6kN0z2Ff9H9xvZMMeaRZxsdKLPDlA8eE67kqd+wBcaUViNh9jz8 AqbNl4tpVG5tKZLwPgcx+8txlJBA66NdOCXSs1qMoDZwCciorg75jvTtxGdmKY12KpNQ pHB94/vlFNH68m5BQ+HEJabJSxZ42jC8pt//z0apCHVpPHU4gfHTsjln1vUBoO2tRES2 zyY2vxzJ7D+TOYf9rtiNF0p8M5Kerhc1/weYRBta49natTPdMP1q2aRWFrNCc6fa/P4h k562Vs6lNEA+ACa1t/4Genn+3Y731iGEKSgWAggn6jkqKqb2MFYCoLFiadr3uo+fDhTc uuUw== MIME-Version: 1.0 X-Received: by 10.43.63.15 with SMTP id xc15mr12757298icb.66.1410285774710; Tue, 09 Sep 2014 11:02:54 -0700 (PDT) Received: by 10.64.229.45 with HTTP; Tue, 9 Sep 2014 11:02:54 -0700 (PDT) Date: Wed, 10 Sep 2014 02:02:54 +0800 Message-ID: Subject: hardware sizing for cassandra From: Oleg Ruchovets To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=bcaec51d2a34a22e820502a5beee X-Virus-Checked: Checked by ClamAV on apache.org --bcaec51d2a34a22e820502a5beee Content-Type: text/plain; charset=UTF-8 Hi , Where can I find the document with best practices about sizing for cassandra deployment? We have 1000 writes / reads per second. record size 1k. Questions: 1) how many machines do we need? 2) how many ram ,disc size / type? 3) What should be network? I understand that hardware is very depends on data distribution and access pattern and other criteria, but I still want to believe that there is a best practice :-) Thanks Oleg. --bcaec51d2a34a22e820502a5beee Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi ,=C2=A0
=C2=A0 =C2=A0Where can I find the document = with best practices about sizing for cassandra deployment?
=C2=A0= =C2=A0We have 1000 writes / reads per second. record size 1k.=C2=A0
<= div>
Questions:
=C2=A0 =C2=A01) how many machines d= o we need?
=C2=A0 =C2=A02) how many ram ,disc size / type?
<= div>=C2=A0 =C2=A03) What should be network?

I unde= rstand that hardware is very depends on data distribution and access patter= n and other criteria, but I still want to believe that there is a best prac= tice :-)=C2=A0

Thanks
Oleg.
--bcaec51d2a34a22e820502a5beee--