Return-Path: Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: (qmail 76187 invoked from network); 27 Sep 2010 22:22:37 -0000 Received: from unknown (HELO mail.apache.org) (::) by ::ffff:140.211.11.9 with SMTP; 27 Sep 2010 22:22:37 -0000 Received: (qmail 30199 invoked by uid 500); 27 Sep 2010 22:22:35 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 30152 invoked by uid 500); 27 Sep 2010 22:22:35 -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 30144 invoked by uid 99); 27 Sep 2010 22:22:35 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 27 Sep 2010 22:22:35 +0000 X-ASF-Spam-Status: No, hits=0.7 required=10.0 tests=RCVD_IN_DNSWL_NONE,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [74.125.82.44] (HELO mail-ww0-f44.google.com) (74.125.82.44) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 27 Sep 2010 22:22:29 +0000 Received: by wwj40 with SMTP id 40so96271wwj.25 for ; Mon, 27 Sep 2010 15:22:08 -0700 (PDT) Received: by 10.216.46.15 with SMTP id q15mr6761512web.103.1285626104229; Mon, 27 Sep 2010 15:21:44 -0700 (PDT) MIME-Version: 1.0 Received: by 10.216.48.195 with HTTP; Mon, 27 Sep 2010 15:21:24 -0700 (PDT) In-Reply-To: <4CA1173E.7000401@pdf.com> References: <4C940305.7070905@pdf.com> <4C9805FD.6000802@pdf.com> <4C9D2015.40002@pdf.com> <4C9D3043.5060100@pdf.com> <4CA0F74E.6070105@pdf.com> <4CA1173E.7000401@pdf.com> From: Benjamin Black Date: Mon, 27 Sep 2010 15:21:24 -0700 Message-ID: Subject: Re: 0.7 memory usage problem To: user@cassandra.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org Does that mean you are doing 600 rows/sec per process or 600/sec total across all processes? On Mon, Sep 27, 2010 at 3:14 PM, Alaa Zubaidi wrote: > =A0Its actually split to 8 different processes that are doing the inserti= on. > > Thanks > > On 9/27/2010 2:03 PM, Peter Schuller wrote: >> >> [note: i put user@ back on CC but I'm not quoting the source code] >> >>> Here is the code I am using (this is only for testing Cassandra it is n= ot >>> going the be used in production) I am new to Java, but I tested this an= d >>> it >>> seems to work fine when running for short amount of time: >> >> If you mean to ask about how to distributed writes - the general >> recommendation is to use a high-level Cassandra client (such as Hector >> at http://github.com/rantav/hector or Pelops at >> http://github.com/s7/scale7-pelops) rather than using the Thrift API >> directly. This is probably especially a good idea if you're new to >> Java as you say. >> >> But in any case, if you're having performance issues w.r.t. the write >> speed - are you in fact doing writes concurrently or is it a single >> sequential client doing the insertions? If you are maxing out without >> being disk bound, make sure that in addition to spreading writes >> across all nodes in the cluster, you are submitting writes with >> sufficient concurrency to allow Cassandra to scale to use available >> CPU across all cores. >> > > -- > Alaa Zubaidi > PDF Solutions, Inc. > 333 West San Carlos Street, Suite 700 > San Jose, CA 95110 =A0USA > Tel: 408-283-5639 (or 408-280-7900 x5639) > fax: 408-938-6479 > email: alaa.zubaidi@pdf.com > > >