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 8A17A17CB0 for ; Thu, 6 Nov 2014 21:08:41 +0000 (UTC) Received: (qmail 79690 invoked by uid 500); 6 Nov 2014 21:08:37 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 79656 invoked by uid 500); 6 Nov 2014 21:08:36 -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 79646 invoked by uid 99); 6 Nov 2014 21:08:36 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 06 Nov 2014 21:08:36 +0000 X-ASF-Spam-Status: No, hits=3.1 required=5.0 tests=HK_RANDOM_ENVFROM,HK_RANDOM_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,T_REMOTE_IMAGE X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of jeeyoungk@gmail.com designates 209.85.192.41 as permitted sender) Received: from [209.85.192.41] (HELO mail-qg0-f41.google.com) (209.85.192.41) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 06 Nov 2014 21:08:11 +0000 Received: by mail-qg0-f41.google.com with SMTP id q107so1435459qgd.28 for ; Thu, 06 Nov 2014 13:05:55 -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=cvNxMQQ/YezkOYTC06RlTqZuOGvi8hV6TnTtYNU1eJk=; b=sKVPA0uAtpd9Cl9mrt1xgFKrje6EhrDY2OSvok58vE0nNWdiSEFx1K8lrzJpUrLRsy i/ZYHWb9gNiPlPijpmmCrJe84jlc4K4CG1+3uIC9bPXEoC19s7MzxkLhqj3upTaAnzhY g493uTsnGnbtW9qCHEqPL3TGTgSJ1TO3gV3M7R7esi6wMi5fCBkpK3YjH/P21nmQ0X9Q XvmSZXTEZjiYkACuEmVmG7oA+q8hYTF88XbpM9GhCSnDfCqocl6dr9rs7Fu47kXssJ3f dBVloEobpLLycX54GW/Zn7LELmElWGszUrM4WZwjEutPJXXVqUXq+Nsks9URs4toDxI+ 3Z9w== X-Received: by 10.140.38.102 with SMTP id s93mr10763106qgs.8.1415307954938; Thu, 06 Nov 2014 13:05:54 -0800 (PST) MIME-Version: 1.0 Received: by 10.140.22.179 with HTTP; Thu, 6 Nov 2014 13:05:22 -0800 (PST) In-Reply-To: References: From: jeeyoung kim Date: Thu, 6 Nov 2014 13:05:22 -0800 Message-ID: Subject: Re: C* on Fusion IO To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=001a11c125ece7068c0507370fe0 X-Virus-Checked: Checked by ClamAV on apache.org --001a11c125ece7068c0507370fe0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable I've been running with FIOs and we've been CPU bound most of the time. But I'm not using native transport yet, and is hoping that it would make things faster. On Thu, Nov 6, 2014 at 12:54 PM, Christopher Brodt wrote: > You should get pretty great performance with those FusionIO cards. One > thing I watch out for whenever scaling Cassandra vertically is compaction > times, which probably won't matter here. However, you have to take into > account that you lose some resiliency to failures with less nodes. > > On Thu, Nov 6, 2014 at 2:48 PM, Russ Bradberry > wrote: > >> I've heard of people running dense nodes (8+ TB) using fusion I/O, but >> with 10GBe connections. I mean why buy a Ferrari and never leave first g= ear? >> >> As far as saturating the network goes, I guess that all depends on your >> workload, and how often you need to repair. >> >> Sent from my iPhone >> >> On Nov 6, 2014, at 3:40 PM, Kevin Burton wrote: >> >> We=E2=80=99re looking at switching data centers and they=E2=80=99re offe= ring pretty >> aggressive pricing on boxes with fusion IO cards. >> >> 2x 1.2TB Fusion IO >> 128GB RAM >> 20 cores. >> >> now.. this isn=E2=80=99t the typical cassandra box. Most people are run= ning >> multiple nodes to scale out vs scale vertically. But these boxes are >> priced aggressively and honestly I think that cassandra would be able to >> saturate the gigabit ethernet port on these machines. >> >> so it *might* be that these are TOO powerful in a way. >> >> Curious if others are running in this config and what tuning options wer= e >> required to get it to work. >> >> Kevin >> >> -- >> >> Founder/CEO Spinn3r.com >> Location: *San Francisco, CA* >> blog: http://burtonator.wordpress.com >> =E2=80=A6 or check out my Google+ profile >> >> >> >> > --=20 Jeeyoung Kim http://kimjeeyoung.com/ --001a11c125ece7068c0507370fe0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I've been running with FIOs and we've been CPU bou= nd most of the time. But I'm not using native transport yet, and is hop= ing that it would make things faster.

<= div class=3D"gmail_quote">On Thu, Nov 6, 2014 at 12:54 PM, Christopher Brod= t <chris@uberbrodt.net> wrote:
You should get pretty great performance with those = FusionIO cards. One thing I watch out for whenever scaling Cassandra vertic= ally is compaction times, which probably won't matter here. However, yo= u have to take into account that you lose some resiliency to failures with = less nodes.

On Thu, Nov 6, 2014 at 2:48 PM,= Russ Bradberry <rbradberry@gmail.com> wrote:
I've heard of people runn= ing dense nodes (8+ TB) using fusion I/O, but with 10GBe connections. I mea= n why buy a Ferrari and never leave first gear?

As= far as saturating the network goes, I guess that all depends on your workl= oad, and how often you need to repair.

Sent from my iPhone

On Nov 6, 2014, at 3:40 PM, Kevin Burton <burton@spinn3r.com> wrote:<= br>
We=E2=80=99re = looking at switching data centers and they=E2=80=99re offering pretty aggre= ssive pricing on boxes with fusion IO cards.

2x 1.2TB Fu= sion IO
128GB RAM
20 cores.

no= w.. this isn=E2=80=99t the typical cassandra box.=C2=A0 Most people are run= ning multiple nodes to scale out vs scale vertically.=C2=A0 But these boxes= are priced aggressively and honestly I think that cassandra would be able = to saturate the gigabit ethernet port on these machines.

so it *might* be that these are TOO powerful in a way.=C2=A0

Curious if others are running in this config and what tun= ing options were required to get it to work.

Kevin=

--

Founder/CEO=C2=A0Spinn3r.com
Location:=C2=A0San Francisco, CA
=
=E2=80=A6 or check out my Google+ profile





--
=
Jeeyoung Kim

=
--001a11c125ece7068c0507370fe0--