I do profile my vert.x based http service and noticed in JMC that all my envelop threads(aka verticles) produce lots of "Java Monitor Blocked" events in class io.vertx.core.http.impl.Http1xServerConnection. Javadoc of this class says: "The internal state is protected using the synchronized keyword. If always used on the same event loop, then we benefit from biased locking which makes the overhead of synchronized near zero.". I noticed that JDK17 I use has BiasedLocking turned off. I try to run test with turned on BiasedLocking but nothing changed. It also says that BiasedLocking was deprecated and could be removed. In the internet I found this SO topic which says that it's fine that vert.x uses synchronized in some classes Does Vert.x have plans addressing the deprecation of biased locking in Java 15?
My question is that does the JMC profile looks good or I should worry and there is a performance issues in my code? 