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 ED03E102FD for ; Tue, 24 Dec 2013 13:41:41 +0000 (UTC) Received: (qmail 57964 invoked by uid 500); 24 Dec 2013 13:41:00 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 57663 invoked by uid 500); 24 Dec 2013 13:40:38 -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 57604 invoked by uid 99); 24 Dec 2013 13:40:33 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 24 Dec 2013 13:40:33 +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 pangaref@gmail.com designates 209.85.223.195 as permitted sender) Received: from [209.85.223.195] (HELO mail-ie0-f195.google.com) (209.85.223.195) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 24 Dec 2013 13:40:30 +0000 Received: by mail-ie0-f195.google.com with SMTP id at1so2904876iec.10 for ; Tue, 24 Dec 2013 05:40:09 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=dTk667ktBrr/g+KHpqY+2m+t/PP8QyevOL7dVw548sY=; b=a+JiOb7JjH4TLbraMpShaFtCe2whicG8bvgT9NeCEOW9LavXqSG9xz51WFWMG0etxd ImVSG+seuSVj38qp12L/ugZ/Ii6FCF8cO/CbUD580zsAo42xmAQk6lQFATVhLkvmRGAa R3/MELRAn7SAI0UWyBeIKnXKKJe+3/ieCOolRVJJHouMmgIacfGRWxmpbBfCWoVEWpaB q5t48hYLtQNIzyQA0Sg1pwh2tslhzIeHsFr1wh0eqGO0fzgwJuxeFnGqid46gzZ870Mb zjwjEsVli7muC5A9AQfVSuzt2vaDfJ4UAt/u5e2YTuQsXdt7oCvc2wlHY5DHqHEFZrny 5e+w== MIME-Version: 1.0 X-Received: by 10.50.78.199 with SMTP id d7mr25900558igx.8.1387892409228; Tue, 24 Dec 2013 05:40:09 -0800 (PST) Received: by 10.64.223.230 with HTTP; Tue, 24 Dec 2013 05:40:09 -0800 (PST) In-Reply-To: <643EA124-D901-443F-BE64-E45AB01F122E@thelastpickle.com> References: <643EA124-D901-443F-BE64-E45AB01F122E@thelastpickle.com> Date: Tue, 24 Dec 2013 15:40:09 +0200 Message-ID: Subject: Re: Best way to measure write throughput... From: Panagiotis Garefalakis To: user@cassandra.apache.org Content-Type: multipart/alternative; boundary=089e013c6ee409e31d04ee47e274 X-Virus-Checked: Checked by ClamAV on apache.org --089e013c6ee409e31d04ee47e274 Content-Type: text/plain; charset=ISO-8859-1 you could always use a benchmark like YCSB https://github.com/brianfrankcooper/YCSB/wiki with a write workload to get a clearer view of you systems throughtput. You can configure the size of the data being inserted (1500 bytes if you are talking about IP packets) to match to your needs. Regargs, Panagiotis Garefalakis On Mon, Dec 23, 2013 at 10:05 PM, Aaron Morton wrote: > nodetool proxyhistograms shows the throughput for the node, nodetool > cfhistograms shows it for a single node. > > If you want to get an overview install something like Ops Centre > http://www.datastax.com/what-we-offer/products-services/datastax-opscenter > > Cheers > > ----------------- > Aaron Morton > New Zealand > @aaronmorton > > Co-Founder & Principal Consultant > Apache Cassandra Consulting > http://www.thelastpickle.com > > On 19/12/2013, at 8:46 pm, Jason Wee wrote: > > Hello, you could also probably do it in your application? Just sample with > an interval of time and that should give some indication of throughput. > > HTH > > /Jason > > > On Thu, Dec 19, 2013 at 12:11 AM, Krishna Chaitanya < > bnsk1990rulz@gmail.com> wrote: > >> Hello, >> >> Could you please suggest to me the best way to measure write-throughput >> in Cassandra. I basically have an application that stores network packets >> to a Cassandra cluster. Which is the best way to measure write performance, >> especially write-throughput, in terms of number of packets stored into >> Cassandra per second or something similar to this??? Can I measure this >> using nodetool? >> >> Thanks. >> >> -- >> Regards, >> BNSK >> *. * >> > > > --089e013c6ee409e31d04ee47e274 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
you could always use a benchmark like YCSB=A0https://github.com/brianfrankc= ooper/YCSB/wiki=A0
with a write workload to get a clearer view of y= ou systems throughtput.=A0
You can configure the size of the data being inserted (1500 bytes if y= ou are talking about IP packets) to match to your needs.

Regargs,
Panagiotis Garefalakis


On Mon, Dec 23, 2013 at 10:05 PM, Aaron = Morton <aaron@thelastpickle.com> wrote:
nodetool proxyhistograms shows the thro= ughput for the node, nodetool cfhistograms shows it for a single node.=A0
If you want to get an overview install something like Ops= Centre=A0http://www.datastax.com/what-we-off= er/products-services/datastax-opscenter

Cheers

-----------------
Aaron Morton
New Zealand
@aaronmorton

Co-Founder & Principal Consult= ant
Apache Cassandra Consulting

On 19/12/2013, at 8:46 pm, Jason Wee <peichieh@gmail.com> wrote:
=
Hello, you could also probab= ly do it in your application? Just sample with an interval of time and that= should give some indication of throughput.

HTH

/Jason


On Thu,= Dec 19, 2013 at 12:11 AM, Krishna Chaitanya <bnsk1990rulz@gmail.com= > wrote:
Hello,

Could you please suggest to me the best way to measure write-throughput = in Cassandra. I basically have an application that stores network packets t= o a Cassandra cluster. Which is the best way to measure write performance, = especially write-throughput, in terms of number of packets stored into Cass= andra per second or something similar to this??? Can I measure this using n= odetool?

Thanks.

-= -
Regards,
BNSK.



--089e013c6ee409e31d04ee47e274--