epollWait blocks ,but why consume cpu
jeremymanson at google.com
Sat May 10 04:44:56 UTC 2014
Are you sure it consumes CPU? I've always found that epollwait blocks, but
the JVM doesn't know it is supposed to change the state of the thread.
This is one of the major reasons that thread dump based profilers are
On Fri, May 9, 2014 at 1:26 AM, Alan Bateman <Alan.Bateman at oracle.com>wrote:
> On 09/05/2014 08:28, fuyou wrote:
>> I use the NetBeans profiler ,the result in attach.
>> Which JDK build is this? I don't think we've had any reports of Selector
> spinning issues in some time.
More information about the core-libs-dev