From cassandra-user-return-1718-apmail-incubator-cassandra-user-archive=incubator.apache.org@incubator.apache.org Tue Dec 08 16:18:56 2009 Return-Path: Delivered-To: apmail-incubator-cassandra-user-archive@minotaur.apache.org Received: (qmail 79463 invoked from network); 8 Dec 2009 16:18:56 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 8 Dec 2009 16:18:56 -0000 Received: (qmail 21802 invoked by uid 500); 8 Dec 2009 16:18:56 -0000 Delivered-To: apmail-incubator-cassandra-user-archive@incubator.apache.org Received: (qmail 21765 invoked by uid 500); 8 Dec 2009 16:18:55 -0000 Mailing-List: contact cassandra-user-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: cassandra-user@incubator.apache.org Delivered-To: mailing list cassandra-user@incubator.apache.org Received: (qmail 21756 invoked by uid 99); 8 Dec 2009 16:18:55 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 08 Dec 2009 16:18:55 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of jbellis@gmail.com designates 74.125.78.146 as permitted sender) Received: from [74.125.78.146] (HELO ey-out-1920.google.com) (74.125.78.146) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 08 Dec 2009 16:18:48 +0000 Received: by ey-out-1920.google.com with SMTP id 3so645030eyh.8 for ; Tue, 08 Dec 2009 08:18:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :from:date:message-id:subject:to:content-type :content-transfer-encoding; bh=hscsCcMn66KAi/BG8PXn3z3RB28qiiVphWxL+2ooFC0=; b=jrOvB/ki47sryV6Y9eWypXSOp4nsvkwPbYu7YtjnXo4Pm9b/Oh2j2txmJh5swIUZNg kZZ4TfvfFO4yUQjWYdr01gWruPvh1RCuDO1C5u+N5NUjhmK/V6Jt5cqn8DUXQN46oXHy hZYznKPQlsdqCXylLnxsvhGCxUIBGgFNbqsuY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type:content-transfer-encoding; b=J9chPOm9jGBLS/JHHGwFEWIWJhu7KMDbiAK2WsAz7E1jyiqKcX/wK2jxv9O4dbca9e RXPhZHDE8JBhKDi34dGe++jVCUL/Ljgxydpa0flPwR6wsOiwm4hTINlJGzwtNW8eeg8m UDLNw1ZM7UjED8nFcnZxZynfgdYYSnQjWvZBg= MIME-Version: 1.0 Received: by 10.216.85.194 with SMTP id u44mr703324wee.65.1260289108248; Tue, 08 Dec 2009 08:18:28 -0800 (PST) In-Reply-To: <93290460-A0BF-4501-8F52-9FA95B7A9549@wooga.net> References: <58E59B99-799C-4A82-B446-E92E6C68CF33@wooga.net> <93290460-A0BF-4501-8F52-9FA95B7A9549@wooga.net> From: Jonathan Ellis Date: Tue, 8 Dec 2009 10:18:08 -0600 Message-ID: Subject: Re: Very simple benchmark - are this typical numbers? To: cassandra-user@incubator.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org can you reproduce using stress.py ? On Tue, Dec 8, 2009 at 10:16 AM, Timo Nentwig wrot= e: > On Dec 7, 2009, at 7:23 PM, Jonathan Ellis wrote: > >> same thing, you are going to need multiple threads to max it out > > I created up to 100 threads and read randomly. Some speed up but not actu= ally mentionable. The threads didn't load the CPU mentionably either. I not= iced that the thread dump was full of Thift (TBinaryProtocol something) Inp= utStream.read(), 10MiB constant read from HD. > >> but yes, reads are typically slower than writes in cassandra because >> of how the log-based merge structures work >> >> On Mon, Dec 7, 2009 at 11:09 AM, Timo Nentwig w= rote: >>> >>> On Dec 7, 2009, at 5:59 PM, Jonathan Ellis wrote: >>> >>>> yes and no -- that's about 4200/s, which is typical for only a single >>> >>> When writing, yes. But I would expect reading to be much faster (?). Re= -executing the read test doesn't speed up things either (I/O caches). >>> >>>> thread but 1/3 to 1/5 of what you'd expect it to max out (on our >>>> quad-core test boxes) when you add client threads >>>> >>>> On Mon, Dec 7, 2009 at 10:38 AM, Timo Nentwig = wrote: >>>>> Hi! >>>>> >>>>> I just downloaded, installed, start cassandra and ran very simple "be= nchmark": write n times something with key=3D=3Dvalue=3D=3DtestInsertAndGet= AndRemove_n (one thread). >>>>> >>>>> For n=3D=3D10 million on a 7200rpm HDD (4G RAM - there should have be= "reasonably" free mem however I didn't check) this took 40min (insert()ing= one after another). Reading them one by one in sequence delivers about 100= /s, reading in 1.000er batches (i.e. multigetColumn()) takes 5-10s (dependi= ng on n, the higher the slower). >>>>> >>>>> Are this typical numbers for cassandra (0.5)? I actually took the con= figuration as it was. >>> >>> > >