[
https://issues.apache.org/jira/browse/CASSANDRA-8835?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14329430#comment-14329430
]
Pavel Yaskevich commented on CASSANDRA-8835:
--------------------------------------------
[~rbranson] I think it might be actually related to epoll behavior that Netty
observed some time again when they put back-off mechanism into the select(..)
code, I will try to do the same thing and give you a patch which would be on
top of 0.3.8 so you can test it out.
> 100% CPU spikes from disruptor thrift server
> --------------------------------------------
>
> Key: CASSANDRA-8835
> URL: https://issues.apache.org/jira/browse/CASSANDRA-8835
> Project: Cassandra
> Issue Type: Bug
> Components: Core
> Environment: 2.0.11, hsha, JDK7u65, ~6,000 connections per machine
> Reporter: Rick Branson
> Assignee: Pavel Yaskevich
>
> Seeing big CPU spikes (to 100%) inside of the TDisruptorServer when running
> hsha. perf top loaded with JVM symbols shows this one floating to the top for
> anywhere between 15 and 90 seconds and then falling down:
> Lcom/thinkaurelius/thrift/TDisruptorServer$SelectorThread;.selectorIterationComplete
> in Lcom/thinkaurelius/thrift/TDisruptorServer$AbstractSelectorThread;.select
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
