Return-Path: Delivered-To: apmail-cassandra-user-archive@www.apache.org Received: (qmail 2155 invoked from network); 4 Jun 2010 19:48:33 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 4 Jun 2010 19:48:33 -0000 Received: (qmail 9829 invoked by uid 500); 4 Jun 2010 19:48:32 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 9810 invoked by uid 500); 4 Jun 2010 19:48:32 -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 9802 invoked by uid 99); 4 Jun 2010 19:48:32 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 04 Jun 2010 19:48:32 +0000 X-ASF-Spam-Status: No, hits=0.3 required=10.0 tests=AWL,RCVD_IN_DNSWL_NONE,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [209.85.219.221] (HELO mail-ew0-f221.google.com) (209.85.219.221) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 04 Jun 2010 19:48:26 +0000 Received: by ewy21 with SMTP id 21so400705ewy.27 for ; Fri, 04 Jun 2010 12:48:05 -0700 (PDT) MIME-Version: 1.0 Received: by 10.213.25.138 with SMTP id z10mr902440ebb.0.1275680885071; Fri, 04 Jun 2010 12:48:05 -0700 (PDT) Received: by 10.213.9.129 with HTTP; Fri, 4 Jun 2010 12:48:05 -0700 (PDT) In-Reply-To: References: <1FCCC842-2F1F-4468-AB93-1A73FE9CD18A@trifork.com> Date: Fri, 4 Jun 2010 21:48:05 +0200 Message-ID: Subject: Re: Are 6..8 seconds to read 23.000 small rows - as it should be? From: Torsten Curdt To: user@cassandra.apache.org Content-Type: text/plain; charset=ISO-8859-1 > Yes, I know. And I might end up doing this in the end. I do though have pretty hard upper limits of how many rows I will end up with for each key, but anyways it might be a good idea none the less. Thanks for the advice on that one. You set count to Integer.MAX. Did you try with say 30000? IIRC that makes a difference (while it shouldn't) even when you have still less than 30000. Paging is the way to go. cheers -- Torsten