Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (athena.apache.org: domain of jbellis@gmail.com designates
 209.85.161.44 as permitted sender)
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;
        b=vw/E3lrhGr+DG5nY1a9yQma9mBcvm0keISIzgtG5rW1i0c+efvYMb9ZqWvZnhyHh0A
         EpHPRfvzAK5Br8YO0ckiZWcztsXzLc4RjZN3ilGDuaCbObFMEIbCZyX4xVSXnDn5yL4C
         ombqQ6i3DKJsUtES1GZ8ctT+XdFOqfUsR9Tpo=
MIME-Version: 1.0
In-Reply-To: <AANLkTinxE4GSiZJBLiskC-zoGFg7mCKT0=-m3jWuvv2h@mail.gmail.com>
References: <AANLkTinxE4GSiZJBLiskC-zoGFg7mCKT0=-m3jWuvv2h@mail.gmail.com>
Date: Tue, 19 Oct 2010 12:18:21 -0500
Message-ID: <AANLkTimpL475-DrecqZeBVs233H_-188KUGfDr7av9-=@mail.gmail.com>
Subject: Re: Read Latency
From: Jonathan Ellis <jbellis@gmail.com>
To: user <user@cassandra.apache.org>
Content-Type: text/plain; charset=ISO-8859-1

I would expect C++ or Java to be substantially faster than Python.
However, I note that Hector (and I believe Pelops) don't yet use the
newest, fastest Thrift library.

On Tue, Oct 19, 2010 at 8:21 AM, Wayne <wav100@gmail.com> wrote:
> The changes seems to do the trick. We are down to about 1/2 of the original
> quorum read performance. I did not see any more errors.
>
> More than 3 seconds on the client side is still not acceptable to us. We
> need the data in Python, but would we be better off going through Java or
> something else to increase performance? All three seconds are taken up in
> Thrift itself (fastbinary.decode_binary(self, iprot.trans, (self.__class__,
> self.thrift_spec))) so I am not sure what other options we have.
>
> Thanks for your help.
>


-- 
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder of Riptano, the source for professional Cassandra support
http://riptano.com