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" t
Aaron
From the CPU samples report. Here is the parts of the CPU samples report
(-Xrunhprof:cpu=samples, depth=4).
TRACE 300668:
java.net.SocketInputStream.socketRead0(SocketInputStream.java:Unknown
line)
java.net.SocketInputStream.read(SocketInputStream.java:129)
org.a
How are you deciding what is thrift ? Thrift is used to handle connections and
serialize / de-serialize off the wire.
Cheers
-
Aaron Morton
Freelance Cassandra Developer
@aaronmorton
http://www.thelastpickle.com
On 27/09/2011, at 2:32 AM, Baskar Duraikannu wrote:
> Hello
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
