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 JEREMIAH.JORDAN@morningstar.com
 designates 216.228.224.32 as permitted sender)
Message-ID: <4E80EA64.5070105@morningstar.com>
Date: Mon, 26 Sep 2011 16:11:00 -0500
From: Jeremiah Jordan <jeremiah.jordan@morningstar.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:6.0.2) Gecko/20110906 Thunderbird/6.0.2
MIME-Version: 1.0
To: user@cassandra.apache.org
Subject: Re: Thrift CPU Usage
References: <4BE0A38A-E7C9-4E55-B4DC-05CD70E316DB@gmail.com>
In-Reply-To: <4BE0A38A-E7C9-4E55-B4DC-05CD70E316DB@gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Yes.  All the stress tool does is flood data through the API, no real 
processing or anything happens.  So thrift reading/writing data should 
be the majority of the CPU time...

On 09/26/2011 08:32 AM, Baskar Duraikannu wrote:
> Hello -
>
> I have been running read tests on Cassandra using "stress" tool.  I have been noticing that thrift seems to be taking lot of CPU over 70% when I look at the "CPU samples" report. Is this normal?
>
> CPU usage seems to go down by 5 to 10% when I change the RPC from "sync" to "async".  Is this normal?
>
> I am running Cassandra 0.8.4 on Cent OS 5.6 ( Kernel 2.6.18.238) and Oracle JVM.
>
> -
> Thanks
> Baskar Duraikannu