Closed holledauer closed 2 years ago
I am personally fine with the 2nd workaround for the time being as our k8s setup also publishes these metrics on pod and instance level. Thus leaving these out while still being able to use the latest micrometer libs is good enough in our case.
I'll close this, as the issue is fixed w/ GraalVM 22.2, and there are several noted workarounds.
Describe the bug
When upgrading to any Quarkus 2.1.* version the cpu usage increases 10x (just the base load without any requests).
Expected behavior
There shouldn't be an increase in cpu usage
Actual behavior
In the image you can see the cpu load for Quarkus 2.0.2.Final and 2.1.2.Final (low cpu usage is 2.0.2.Final)
How to Reproduce?
No response
Output of
uname -a
orver
No response
Output of
java -version
GraalVM 21.2.0 Java 11 CE
GraalVM version (if different from Java)
GraalVM 21.2.0 Java 11 CE
Quarkus version or git rev
2.1.2.Final
Build tool (ie. output of
mvnw --version
orgradlew --version
)Gradle 6.6.1
Additional information
No response