Return-Path: Delivered-To: apmail-incubator-cassandra-user-archive@minotaur.apache.org Received: (qmail 70057 invoked from network); 6 Oct 2009 16:42:37 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 6 Oct 2009 16:42:37 -0000 Received: (qmail 59387 invoked by uid 500); 6 Oct 2009 16:42:36 -0000 Delivered-To: apmail-incubator-cassandra-user-archive@incubator.apache.org Received: (qmail 59372 invoked by uid 500); 6 Oct 2009 16:42:36 -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 59363 invoked by uid 99); 6 Oct 2009 16:42:36 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 Oct 2009 16:42:36 +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 209.85.219.205 as permitted sender) Received: from [209.85.219.205] (HELO mail-ew0-f205.google.com) (209.85.219.205) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 06 Oct 2009 16:42:27 +0000 Received: by ewy1 with SMTP id 1so3534546ewy.34 for ; Tue, 06 Oct 2009 09:41:07 -0700 (PDT) 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 :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=oQXnc+WFXPsQ1P/jaRj8hGGf6QFea4Icn4Ke1ukEg84=; b=jTuQHytDjYlLUhHt0m5+2UXASaY0br9HxEjpTbD7DgRxv3R2niyO2CHv8FRvs3CebE J/DyQdtiQ7R94lzzDs8dg9vweeo4gFHe55T7OcmaMn+Q+i2Xr8Wek/o3KBjeLabt1rnH cDjdlG1i4uF1n5qbfYxk+45Ov8cDgxB0nVE3s= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=fMnO6hzQD0zFHR19ibgfIPnTZMQrdfETfUZH2KM9F6bC2juHXshrUlGOfBtOspD6mS PAhWoSJu/R7o8AxAQYKn8afVu/jqtMvsPvInSJGW/v2Kwl+7nUk5wIoYI/lGL02fe6Z8 IYZxH26K/OzJ4rh3DCawzixSma/oWNyiapPn0= MIME-Version: 1.0 Received: by 10.216.87.9 with SMTP id x9mr397818wee.0.1254847266925; Tue, 06 Oct 2009 09:41:06 -0700 (PDT) In-Reply-To: <23b1e84e0910060914v1f1a8865i65244324e0715b56@mail.gmail.com> References: <23b1e84e0910011551h49a6e8a0xaba1d2d6290c42e6@mail.gmail.com> <23b1e84e0910051146q528c1df0r803821dabfe9b61c@mail.gmail.com> <23b1e84e0910051217m75e86a07n5df57d3c5e183fca@mail.gmail.com> <23b1e84e0910060914v1f1a8865i65244324e0715b56@mail.gmail.com> Date: Tue, 6 Oct 2009 11:41:06 -0500 Message-ID: Subject: Re: Storage proxy write latency is too high From: Jonathan Ellis 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 Very interesting. Thanks for figuring that out. -Jonathan On Tue, Oct 6, 2009 at 11:14 AM, Igor Katkov wrote: > I think I finally found what. It's implementation of Java NIOon Windows (= JVM > 1.6.0.16, 64b on Windows 2003) > The very same code, same network but CentOS linux gives almost 4x > performance. (in Cassandra@linux -> Cassandra@Windows setup) > I don't have another linux box to test (Cassandra@linux -> Cassandra@linu= x) > performance, but expect it to be even better. > > A lesson learnt: don't use windows. > > P.S. > Here at Viigo we also learnt the hard way that=A0 async IO is also broken= in > .NET (C#). Now I start to wonder if there is some fundamental flaw in asy= nc > IO on windows... > > On Mon, Oct 5, 2009 at 3:23 PM, Jonathan Ellis wrote: >> >> On Mon, Oct 5, 2009 at 2:17 PM, Igor Katkov wrote: >> > measured via JMX console i.e. does not include client-cassandra-client >> > latency >> > >> > 20 client threads 176975b value StorageProxy.WriteLatency ~660ms >> > 10 client threads 176975b value StorageProxy.WriteLatency ~350ms >> > 05 client threads 176975b value StorageProxy.WriteLatency ~156ms >> >> this is going up basically linearly with amount of (data x clients), >> so clearly something is getting saturated. > >