From user-return-37441-apmail-cassandra-user-archive=cassandra.apache.org@cassandra.apache.org Wed Nov 6 23:36:14 2013 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 4570D10E87 for ; Wed, 6 Nov 2013 23:36:14 +0000 (UTC) Received: (qmail 48749 invoked by uid 500); 6 Nov 2013 23:36:11 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 48720 invoked by uid 500); 6 Nov 2013 23:36:11 -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 48712 invoked by uid 99); 6 Nov 2013 23:36:11 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 Nov 2013 23:36:11 +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 abarua@247-inc.com designates 213.199.154.17 as permitted sender) Received: from [213.199.154.17] (HELO emea01-am1-obe.outbound.protection.outlook.com) (213.199.154.17) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 Nov 2013 23:36:03 +0000 Received: from SINPR03MB139.apcprd03.prod.outlook.com (10.242.53.22) by SINPR03MB140.apcprd03.prod.outlook.com (10.242.53.27) with Microsoft SMTP Server (TLS) id 15.0.815.6; Wed, 6 Nov 2013 23:35:38 +0000 Received: from SINPR03MB139.apcprd03.prod.outlook.com ([169.254.12.167]) by SINPR03MB139.apcprd03.prod.outlook.com ([169.254.12.167]) with mapi id 15.00.0815.000; Wed, 6 Nov 2013 23:35:38 +0000 From: Arindam Barua To: "user@cassandra.apache.org" Subject: Config changes to leverage new hardware Thread-Topic: Config changes to leverage new hardware Thread-Index: Ac7bRPlbHTuTjZ9YTeuV7fShtMd93w== Date: Wed, 6 Nov 2013 23:35:37 +0000 Message-ID: <218c9fe89d68457db021e5559febc6db@SINPR03MB139.apcprd03.prod.outlook.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [66.170.122.252] x-forefront-prvs: 0022134A87 x-forefront-antispam-report: SFV:NSPM;SFS:(164054003)(199002)(189002)(66066001)(81542001)(65816001)(63696002)(50986001)(31966008)(51856001)(77982001)(74316001)(54316002)(56776001)(74366001)(59766001)(4396001)(69226001)(74876001)(54356001)(2656002)(49866001)(87936001)(47736001)(47976001)(81342001)(47446002)(46102001)(53806001)(76176001)(76796001)(76786001)(56816003)(76576001)(77096001)(19300405004)(19609705001)(83072001)(15975445006)(16236675002)(81816001)(74662001)(33646001)(83322001)(87266001)(81686001)(74706001)(15202345003)(80976001)(19580395003)(79102001)(85306002)(24736002);DIR:OUT;SFP:;SCL:1;SRVR:SINPR03MB140;H:SINPR03MB139.apcprd03.prod.outlook.com;CLIP:66.170.122.252;FPR:;RD:InfoNoRecords;A:1;MX:3;LANG:en; Content-Type: multipart/alternative; boundary="_000_218c9fe89d68457db021e5559febc6dbSINPR03MB139apcprd03pro_" MIME-Version: 1.0 X-OriginatorOrg: 247-inc.com X-Virus-Checked: Checked by ClamAV on apache.org --_000_218c9fe89d68457db021e5559febc6dbSINPR03MB139apcprd03pro_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable We want to upgrade our Cassandra cluster to have newer hardware, and were w= ondering if anyone has suggestions on Cassandra or linux config changes tha= t will prove to be beneficial. As of now, our performance tests (our application specific as well as cassa= ndra-stress) are not showing any significant difference in the hardwares, w= hich is a little disheartening, since the new hardware has a lot more RAM a= nd CPU. Old Hardware: 8 cores (2 quad core), 32 GB RAM, four 1-TB disks ( 1 disk us= ed for commitlog and 3 disks RAID 0 for data) New Hardware: 32 cores (2 8-core with hyperthreading), 128 GB RAM, eight 1-= TB disks ( 1 disk used for commitlog and 7 disks RAID 0 for data) Most of the cassandra config currently is the default, and we are using Lev= eledCompaction strategy. Default key cache, row cache turned off. The config we tried modifying so far was concurrent_reads to (16 * number o= f drives) and concurrent_writes to (8 * number of cores) as per recommendat= ion in cassandra.yaml, but that didn't make much difference. We were hoping that at least the extra RAM in the new hardware will be used= for Linux file caching and hence an improvement in performance will be obs= erved. Running Cassandra 1.1.5 currently, but evaluating to upgrade to 1.2.11 soon= . Thanks, Arindam --_000_218c9fe89d68457db021e5559febc6dbSINPR03MB139apcprd03pro_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

 

We want to upgrade our Cassandra cluster to have new= er hardware, and were wondering if anyone has suggestions on Cassandra or l= inux config changes that will prove to be beneficial.

As of now, our performance tests (our application sp= ecific as well as cassandra-stress) are not showing any significant differe= nce in the hardwares, which is a little disheartening, since the new hardwa= re has a lot more RAM and CPU.

 

Old Hardware: 8 cores (2 quad core), 32 GB RAM, four= 1-TB disks ( 1 disk used for commitlog and 3 disks RAID 0 for data)

New Hardware: 32 cores (2 8-core with hyperthreading= ), 128 GB RAM, eight 1-TB disks ( 1 disk used for commitlog and 7 disks RAI= D 0 for data)

 

Most of the cassandra config currently is the defaul= t, and we are using LeveledCompaction strategy. Default key cache, row cach= e turned off.

The config we tried modifying so far was concurrent_= reads to (16 * number of drives) and concurrent_writes to (8 * number of co= res) as per recommendation in cassandra.yaml, but that didn’t make mu= ch difference.

We were hoping that at least the extra RAM in the ne= w hardware will be used for Linux file caching and hence an improvement in = performance will be observed.

 

Running Cassandra 1.1.5 currently, but evaluating to= upgrade to 1.2.11 soon.

 

Thanks,

Arindam

--_000_218c9fe89d68457db021e5559febc6dbSINPR03MB139apcprd03pro_--