Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

100% CPU in epoll_wait #4241

Closed
rvansa opened this issue Sep 27, 2019 · 2 comments · Fixed by #4242
Closed

100% CPU in epoll_wait #4241

rvansa opened this issue Sep 27, 2019 · 2 comments · Fixed by #4242
Assignees
Labels
kind/bug Something isn't working
Milestone

Comments

@rvansa
Copy link
Contributor

rvansa commented Sep 27, 2019

Describe the bug
In some environments, using native image, all threads reading I/O can spend 100% CPU time polling epoll_wait(..., timeout=0). Turns out this is an effect of static final io.netty.util.concurrent.ScheduledFutureTask.START_TIME being set to system-dependent System.nanoTime() during compilation and the NioEventLoop behaving in an unexpected way.

Note that this behaviour cannot be reproduced when compiling and running on the same machine, due to the nature of System.nanoTime() base value.

@rvansa rvansa added the kind/bug Something isn't working label Sep 27, 2019
rvansa added a commit to rvansa/quarkus that referenced this issue Sep 27, 2019
@Sanne
Copy link
Member

Sanne commented Sep 27, 2019

thanks @rvansa ! Pinging @stuartwdouglas as I believe he was looking as well into moving such initializations to runtime.

@rvansa
Copy link
Contributor Author

rvansa commented Sep 27, 2019

Could someone on quarkus-dev ml also ping this user who seems to suffer from the same problem?
https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!msg/quarkus-dev/jjwCQJMV434/mlujuFClAAAJ

@stuartwdouglas stuartwdouglas self-assigned this Sep 27, 2019
rvansa added a commit to rvansa/quarkus that referenced this issue Sep 30, 2019
rvansa added a commit to rvansa/quarkus that referenced this issue Sep 30, 2019
kenfinnigan added a commit that referenced this issue Sep 30, 2019
@gsmet gsmet added this to the 0.23.2 milestone Oct 1, 2019
@gsmet gsmet closed this as completed Oct 1, 2019
gsmet pushed a commit that referenced this issue Oct 1, 2019
gsmet pushed a commit that referenced this issue Oct 2, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something isn't working
Projects
None yet
4 participants