flink-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kruse, Sebastian" <Sebastian.Kr...@hpi.de>
Subject NioEventLoop consumes most of the CPU
Date Tue, 05 May 2015 15:51:09 GMT
Hi everyone,

Everytime when I am running jvisualvm on one of the machines in our cluster during a Flink
job, I see that NioEventLoop.select() is taking 50% to 70% CPU self-time. I wonder how severe
this is. It might be busy-waiting time that cannot be filled otherwise, but I wanted to ask
you if you also faced this issue and/or you know the cause of that circumstance.


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message