Mailing-List: contact user-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: user@cassandra.apache.org
Received-SPF: pass (nike.apache.org: domain of jbellis@gmail.com designates
 74.125.82.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:content-transfer-encoding;
        b=d5pvKBPTdeszKqJX3B9HJvYLT47YdIFYnOQFVNLFrFfa0UhotLSRm/ZLLa109MCA5G
         /WIbDKo3FGOG/jIRAz+jP69dlg3IvpgIcjH3lEKcN3Lixz64NN1Zy+TOPCGSawTV96vB
         VGPSBFYgWqynGPGvtxp6Lf7Z+iWlxzjjDR8hs=
MIME-Version: 1.0
In-Reply-To: <AANLkTi=WOwXcV-9HxUNLzsJUnMb+Q36wkHGpn8XjrBVY@mail.gmail.com>
References: <AANLkTinebvQREj9gB9_Fb8nU0Z-T-MMas5ewqyxDJ8h2@mail.gmail.com>
	<AANLkTimQTVMg0_t+d_2f9Acxgb5vnvzLHPdT=Q7e8MGM@mail.gmail.com>
	<AANLkTikE3_3q23APm3pX=zowfX0L8CtmJrBHpO-ePx3v@mail.gmail.com>
	<AANLkTi=xFmg7WYVDLCsqgjuQHbAeXc2vHvChw2OE379X@mail.gmail.com>
	<AANLkTi=WOwXcV-9HxUNLzsJUnMb+Q36wkHGpn8XjrBVY@mail.gmail.com>
Date: Sat, 16 Oct 2010 08:52:38 -0500
Message-ID: <AANLkTimsgND=azeMLee5WEJpoumuKNJYKt7GJKz+p==0@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
Content-Transfer-Encoding: quoted-printable

Stack trace from cassandra log?

On Sat, Oct 16, 2010 at 6:50 AM, Wayne <wav100@gmail.com> wrote:
> While doing a read I get a TApplicationException: Internal Error processi=
ng
> get_slice.
>
> On Fri, Oct 15, 2010 at 5:49 PM, Jonathan Ellis <jbellis@gmail.com> wrote=
:
>>
>> On Fri, Oct 15, 2010 at 2:21 PM, Wayne <wav100@gmail.com> wrote:
>> > The optimization definitely shaved off some time. Now it is running
>> > about 3x
>> > CFSTATS reported time. Below are the logs.
>> >
>> > There is a ~300ms time frame after the last ResponseVerbHandler prior =
to
>> > the
>> > resolver starting. Based on a quorum read the response resolver should
>> > kick
>> > after 2 reads come in correct? That would mean it waited 500ms before
>> > starting. Where is this time going?
>>
>> It's going to deserialize the replies to see if it has both the data
>> and enough digests to call resolve(). =A0Then resolve deserializes them
>> a 2nd time, so there's an easy win there caching the first
>> deserialize, in the patch attached. =A0(Applies on top of the previous
>> one, which has been committed to the 0.6 svn branch at
>> https://svn.apache.org/repos/asf/cassandra/branches/cassandra-0.6.)
>>
>> > There is still the 3+ second delay between the last 2 entries. Is this
>> > the
>> > thrift server?
>>
>> It's converting the reply from Cassandra's internal representation to
>> thrift, and sending it to the client. =A0I suspect most of the time is
>> the actual sending/waiting for the client to read part. =A0Patch 2 also
>> includes a debug statement after the convert-to-thrift stage to
>> verify.
>>
>> --
>> Jonathan Ellis
>> Project Chair, Apache Cassandra
>> co-founder of Riptano, the source for professional Cassandra support
>> http://riptano.com
>
>


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