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 6BBFBD425 for ; Mon, 1 Oct 2012 15:19:19 +0000 (UTC) Received: (qmail 63524 invoked by uid 500); 1 Oct 2012 15:19:17 -0000 Delivered-To: apmail-cassandra-user-archive@cassandra.apache.org Received: (qmail 63486 invoked by uid 500); 1 Oct 2012 15:19:16 -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 63477 invoked by uid 99); 1 Oct 2012 15:19:16 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 01 Oct 2012 15:19:16 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of woolfel@gmail.com designates 209.85.214.172 as permitted sender) Received: from [209.85.214.172] (HELO mail-ob0-f172.google.com) (209.85.214.172) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 01 Oct 2012 15:19:11 +0000 Received: by obqv19 with SMTP id v19so6154527obq.31 for ; Mon, 01 Oct 2012 08:18:50 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=IPheKFq9OXpSdudK1k7VlIDNKFIoGliY2/9MGnitIeE=; b=Qn8zACQnD1OxrTgcp2fH5zofZIzk5VE9i9YXjbRPZzMzfqWp6Q11OTtAThUv57uraX WLb/2ZErW8+PgDczeI5kO/RlIqtMgrjWKkYwMl9N6y6LPvA8omajTg5YMhbJPMkVhSXs r/mYQuXUuWW99UYpUYSMKP28oyiESWAMJCIFIEXEe615q0JtPQF9a4HigZFPIC2ocOxr q/aIPQfXmGZHDtPEyJgxuJ6WekYeGggERmU761Zk3fhYenv7rYNjQ08DO4JAMF9VAgWG JuK/1nNxQDvdambbJiIV2RYNimxta7k80n1fViFslQpJcEl0qxxtMauqhiweN9l6+Ufa +JXg== MIME-Version: 1.0 Received: by 10.182.212.70 with SMTP id ni6mr12081253obc.44.1349104730400; Mon, 01 Oct 2012 08:18:50 -0700 (PDT) Received: by 10.76.173.200 with HTTP; Mon, 1 Oct 2012 08:18:50 -0700 (PDT) In-Reply-To: References: Date: Mon, 1 Oct 2012 11:18:50 -0400 Message-ID: Subject: Re: Cassandra vs Couchbase benchmarks From: Peter Lin To: user@cassandra.apache.org Content-Type: text/plain; charset=ISO-8859-1 Here is my own experience testing couchdb versus cassandra for an internal application. My test wasn't some dummy test case, it was realistic workloads that is 95% write and 5% read. We insert data in batches to maximize throughput. The critical thing for my use case was to answer "when does the server crash and what happens?" Each row was approximately 4-8K. I tested with a variety of batch sizes and found that couchdb choked around 20K rows of data. When I looked at couchdb logs, there was no indication of why it crashed or what caused it. I tested cassandra up to 50K rows per batch and didn't have time to reach the failure point. The troubling issue for me is the lack of information on the cause of the crash. All server crash at some point. Having details on why and how it crashed to me is critical to debugging and improving performance. Having zero indication for me suggests major architectural flaws and issues in the design and implementation. I haven't had time to investigate the real cause, since the logs didn't give any hint. If the log had details, I would have atleast taken a look at the source file and try to debug it. On Mon, Oct 1, 2012 at 11:05 AM, Andy Cobley wrote: > There are some interesting results in the benchmarks below: > > http://www.slideshare.net/renatko/couchbase-performance-benchmarking > > Without starting a flame war etc, I'm interested if these results should > be considered "Fair and Balanced" or if the methodology is flawed in some > way ? (for instance is the use of Amazon EC2 sensible for Cassandra > deployment) ? > > Andy > > > > The University of Dundee is a Scottish Registered Charity, No. SC015096. > >