From user-return-33762-apmail-cassandra-user-archive=cassandra.apache.org@cassandra.apache.org Fri Apr 26 15:00:09 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 F12D810504 for ; Fri, 26 Apr 2013 15:00:08 +0000 (UTC) Received: (qmail 7742 invoked by uid 500); 26 Apr 2013 15:00:06 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 7712 invoked by uid 500); 26 Apr 2013 15:00:06 -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 7704 invoked by uid 99); 26 Apr 2013 15:00:06 -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 15:00:06 +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 (nike.apache.org: domain of ttemplier@restlet.com designates 74.125.82.46 as permitted sender) Received: from [74.125.82.46] (HELO mail-wg0-f46.google.com) (74.125.82.46) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 26 Apr 2013 14:59:59 +0000 Received: by mail-wg0-f46.google.com with SMTP id e11so2168153wgh.1 for ; Fri, 26 Apr 2013 07:59:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=restlet.com; s=google; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type; bh=Cxdvp81Nti0EERkD0zdcOcKv1wxEeaFTlaIYWyFYEm4=; b=M+G0wcCmQSOCaSBjpoTUCb3WMPc/Cek2tHglBfSmKga2LJHdLv1h2VnObomMxUZnUP jMl+zcN5gpTojRyKQUtLoTvrOxBBscDDoGY5WEQieRz0EQ1/FBlrbdTSbZn38ac3FeFA hyn+WmYRsGlTY/7qEdKVLL7onba8/1m/Qqk4g= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:x-gm-message-state; bh=Cxdvp81Nti0EERkD0zdcOcKv1wxEeaFTlaIYWyFYEm4=; b=FUzo4qNHCwPWXV68kH+1FIR21ke6g9JzFrOo+yXwQXwyoFobfHzgZqGxaIipNueQsH OUAyZn3K+ODEbtxtlEuXG0jMkN4ff2zQspCoRemC7ajJzrwpmEa+dMoIiZITVRL4/001 1T8nAkHoVLAfejw2vnsRa2zj0NyrzvDfeSqgtqm4UUrVe501/zX18fZOI/muP+ydjFnW o8FBNw/CKPTcw2HL0hqJX/E9jQyDLWKhPwGkTP/rID2GdBR3Jr9I+oO0temF1/e9e8+7 3hOz3HDPM3KBTjJGxHN/EYL0kSPULebrSLQ8txGp3bRhFd+4ZE8q6ofzvNL5LMWSp+xH +m4Q== X-Received: by 10.180.183.210 with SMTP id eo18mr4609387wic.17.1366988379544; Fri, 26 Apr 2013 07:59:39 -0700 (PDT) Received: from [192.168.2.6] ([195.101.29.12]) by mx.google.com with ESMTPSA id d8sm4385511wiv.10.2013.04.26.07.59.37 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 26 Apr 2013 07:59:38 -0700 (PDT) Message-ID: <517A964F.4030304@restlet.com> Date: Fri, 26 Apr 2013 16:59:27 +0200 From: Thierry Templier User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130330 Thunderbird/17.0.5 MIME-Version: 1.0 To: user@cassandra.apache.org Subject: Re: Performance / limitations of WHERE ... IN queries References: <5178E965.6020205@restlet.com> <0058652D-939E-4BBE-AE09-98FD32FF50FE@thelastpickle.com> In-Reply-To: <0058652D-939E-4BBE-AE09-98FD32FF50FE@thelastpickle.com> Content-Type: multipart/alternative; boundary="------------080803000803040703070002" X-Gm-Message-State: ALoCoQkJErrobKTBshloJyih+woA6omhHYt0kLdOWo4pmh9EWZuDUObWbP/nTJF1VRolXzSXj9D2 X-Virus-Checked: Checked by ClamAV on apache.org This is a multi-part message in MIME format. --------------080803000803040703070002 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Thanks very much, Aaron, for your answer! Thierry > 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 reqrequests > 100's or 1000's then this can delay other client requests. > > Cheers --------------080803000803040703070002 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit
Thanks very much, Aaron, for your answer!

Thierry
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

--------------080803000803040703070002--