Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Thread.holdsLock calls result in excessive overhead w/o ability to turn it off #5586
When profiling OkHttp3 4.2.1 under a high load (a microservice/RPC scenario), the profiler constantly shows
Here's an example hot spot in
The generated Java source makes the call to
The JIT optimizer is unable to optimize across native call boundaries. This cause a hard unable-to-optimize situation, which, for example, inhibits inlining across virtual calls. In my profiling for my target use case, this placed a ceiling on performance that I was not able to work around (save for building a patched OkHttp version).