-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Investigate if the secondary_super_cache
is stable
#10781
Comments
Here are two reports generated by the type pollution agent: this one from a JVM running the jetty load generator, and that one from a JVM running the jetty server. They were generated on a locally-run benchmark running for 15s with two loaders generating 60k RPS on a single server. Only one of the two loaders' report is included as the two loader reports are nearly identical. |
cc @franz1981 |
FYI just fixed the stack trace level RedHatPerf/type-pollution-agent#18 |
Signed-off-by: Ludovic Orban <lorban@bitronix.be>
#10781 Stabilize secondary_super_cache in server code Signed-off-by: Ludovic Orban <lorban@bitronix.be>
This issue has been automatically marked as stale because it has been a |
Fixed by #10802. |
Jetty version(s)
12.0.x
Enhancement Description
JDK-8180450 was filed because under certain conditions, the JVM's handling of casts to interfaces can cause a noticeable slowdown. RedHat has written an agent to help diagnose if a java piece of code is impacted by this problem or not.
We should investigate if Jetty is impacted by this perf issue with the help of RH's type pollution agent.
The text was updated successfully, but these errors were encountered: