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 246E9B8A8 for ; Fri, 6 Jan 2012 15:51:03 +0000 (UTC) Received: (qmail 27660 invoked by uid 500); 6 Jan 2012 15:51:00 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 27532 invoked by uid 500); 6 Jan 2012 15:51:00 -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 27524 invoked by uid 99); 6 Jan 2012 15:50:59 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 Jan 2012 15:50:59 +0000 X-ASF-Spam-Status: No, hits=1.7 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of tivv00@gmail.com designates 209.85.215.172 as permitted sender) Received: from [209.85.215.172] (HELO mail-ey0-f172.google.com) (209.85.215.172) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 Jan 2012 15:50:51 +0000 Received: by eaak10 with SMTP id k10so1324764eaa.31 for ; Fri, 06 Jan 2012 07:50:30 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type; bh=ubs2ZVyE0ZpAfpHp99s+g7bnwAGulqgqeO3hRurb0XI=; b=AHIdVAlUsggHt1lbWxt/23dLY0cAlYtKOWncK98tfIeFkXFR0sUWPmL6MsteFTJe9W SmLb4utOUzuAUxUQxLl5/qgiIlhEc7XfkvgycxLyBMQlW7jO+l6oi/XGyYBQXtwI4psV SPkRKW4cAubSqeVixs1Y5411mWZHRFFR4z7/g= Received: by 10.205.131.16 with SMTP id ho16mr2770525bkc.105.1325865030676; Fri, 06 Jan 2012 07:50:30 -0800 (PST) Received: from [10.64.1.26] ([94.45.140.16]) by mx.google.com with ESMTPS id ci12sm122067059bkb.13.2012.01.06.07.50.29 (version=TLSv1/SSLv3 cipher=OTHER); Fri, 06 Jan 2012 07:50:29 -0800 (PST) Message-ID: <4F071868.8020104@gmail.com> Date: Fri, 06 Jan 2012 17:51:04 +0200 From: Vitalii Tymchyshyn User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.2.24) Gecko/20111109 Lightning/1.0b2 Thunderbird/3.1.16 MIME-Version: 1.0 To: user@cassandra.apache.org Subject: Re: Should I throttle deletes? References: <4F04C10E.1000904@bnl.gov> <4F05F9C8.5050601@bnl.gov> <4F070268.5030001@gmail.com> In-Reply-To: Content-Type: multipart/alternative; boundary="------------080701040807000106090804" This is a multi-part message in MIME format. --------------080701040807000106090804 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Do you mean on writes? Yes, your timeouts must be so that your write batch could complete until timeout elapsed. But this will lower write load, so reads should not timeout. Best regards, Vitalii Tymchyshym 06.01.12 17:37, Philippe написав(ла): > > But you will then get timeouts. > > Le 6 janv. 2012 15:17, "Vitalii Tymchyshyn" > a écrit : > > 05.01.12 22:29, Philippe написав(ла): >> >> Then I do have a question, what do people generally use as >> the batch size? >> >> I used to do batches from 500 to 2000 like you do. >> After investigating issues such as the one you've encountered >> I've moved to batches of 20 for writes and 256 for reads. >> Everything is a lot smoother : no more timeouts. >> > I'd better reduce mutation thread pool with concurrent_writes > setting. This will lower server load no matter, how many clients > are sending batches, at the same time you still have good batching. > > Best regards, Vitalii Tymchyshyn > --------------080701040807000106090804 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit Do you mean on writes? Yes, your timeouts must be so that your write batch could complete until timeout elapsed. But this will lower write load, so reads should not timeout.

Best regards, Vitalii Tymchyshym

06.01.12 17:37, Philippe написав(ла):

But you will then get timeouts.

Le 6 janv. 2012 15:17, "Vitalii Tymchyshyn" <tivv00@gmail.com> a écrit :
05.01.12 22:29, Philippe написав(ла):
Then I do have a question, what do people generally use as the batch size?
I used to do batches from 500 to 2000 like you do.
After investigating issues such as the one you've encountered I've moved to batches of 20 for writes and 256 for reads. Everything is a lot smoother : no more timeouts.

I'd better reduce mutation thread pool with concurrent_writes setting. This will lower server load no matter, how many clients are sending batches, at the same time you still have good batching.

Best regards, Vitalii Tymchyshyn

--------------080701040807000106090804--