From user-return-33742-apmail-cassandra-user-archive=cassandra.apache.org@cassandra.apache.org Fri Apr 26 02:07:58 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 B4B79F13D for ; Fri, 26 Apr 2013 02:07:58 +0000 (UTC) Received: (qmail 41592 invoked by uid 500); 26 Apr 2013 02:07:56 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 41560 invoked by uid 500); 26 Apr 2013 02:07:56 -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 41552 invoked by uid 99); 26 Apr 2013 02:07:56 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 26 Apr 2013 02:07:56 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [208.113.200.5] (HELO homiemail-a80.g.dreamhost.com) (208.113.200.5) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 26 Apr 2013 02:07:50 +0000 Received: from homiemail-a80.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a80.g.dreamhost.com (Postfix) with ESMTP id 25B2037A076 for ; Thu, 25 Apr 2013 19:07:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=thelastpickle.com; h=from :content-type:message-id:mime-version:subject:date:references:to :in-reply-to; s=thelastpickle.com; bh=Ggtn9+X1S0SsE/HG25DiHFUv3+ w=; b=YLzSNB9ukTwdK0FHP+3c0u5Gn89Xw3MMWJ9SIi+bfXxPT6YxZ9P28qtQlZ GPFiSAMVfbA0WG3PRLuXisn3TA3geVpi0zlggLoLE0FKLFBr+5DU8T6nU3VcJe15 1N95vEvh0UmmF+qPmxUuMjaF73uLwIC594jNOVRweH6J1FDxI= Received: from [172.16.1.8] (unknown [203.86.207.101]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: aaron@thelastpickle.com) by homiemail-a80.g.dreamhost.com (Postfix) with ESMTPSA id 9BFAC37A06F for ; Thu, 25 Apr 2013 19:07:28 -0700 (PDT) From: aaron morton Content-Type: multipart/alternative; boundary="Apple-Mail=_F1A06EB5-30EF-40B1-B632-784C96DABAEE" Message-Id: <0058652D-939E-4BBE-AE09-98FD32FF50FE@thelastpickle.com> Mime-Version: 1.0 (Mac OS X Mail 6.3 \(1503\)) Subject: Re: Performance / limitations of WHERE ... IN queries Date: Fri, 26 Apr 2013 14:07:26 +1200 References: <5178E965.6020205@restlet.com> To: user@cassandra.apache.org In-Reply-To: <5178E965.6020205@restlet.com> X-Mailer: Apple Mail (2.1503) X-Virus-Checked: Checked by ClamAV on apache.org --Apple-Mail=_F1A06EB5-30EF-40B1-B632-784C96DABAEE Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 You are effectively doing a multi get. Getting more than one row at a = time is normally faster, but there will be a drop off point where the = improvements slow down. Run some tests.=20 Also consider that each row you requests creates RF number of commands = spread around the thread pools for the row. If one client req requests = 100's or 1000's then this can delay other client requests.=20 Cheers =20 ----------------- Aaron Morton Freelance Cassandra Consultant New Zealand @aaronmorton http://www.thelastpickle.com On 25/04/2013, at 8:29 PM, Thierry Templier = wrote: > Hello, >=20 > I wonder what are the performances of WHERE ... IN queries especially = when the number of elements in the IN grows? >=20 > Thanks very much for your help! > Thierry --Apple-Mail=_F1A06EB5-30EF-40B1-B632-784C96DABAEE Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=iso-8859-1 You = are effectively doing a multi get. Getting more than one row at a time = is normally faster, but there will be a drop off point where the = improvements slow down. Run some tests. 

Also = consider that each row you requests creates RF number of commands spread = around the thread pools for the row. If one client req requests = 100's or 1000's then this can delay other client = requests. 

Cheers
 
http://www.thelastpickle.com

On 25/04/2013, at 8:29 PM, Thierry Templier <ttemplier@restlet.com> = wrote:

Hello,

I wonder what are the performances of WHERE = ... IN queries especially when the number of elements in the IN = grows?

Thanks very much for your = help!
Thierry

= --Apple-Mail=_F1A06EB5-30EF-40B1-B632-784C96DABAEE--