-
Notifications
You must be signed in to change notification settings - Fork 148
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
String.intern is consuming too much CPU #13
Labels
Comments
jaimecasero
added a commit
to jaimecasero/jain-sip
that referenced
this issue
Nov 2, 2015
jaimecasero
added a commit
to jaimecasero/jain-sip
that referenced
this issue
Nov 4, 2015
jaimecasero
added a commit
to jaimecasero/jain-sip
that referenced
this issue
Nov 24, 2015
xhoaluu
pushed a commit
that referenced
this issue
Oct 31, 2016
Fix right byte order in frame length encoding
AlerantAppNGIN
pushed a commit
to AlerantAppNGIN/jain-sip
that referenced
this issue
May 19, 2017
Rationale: too much CPU overhead, see Restcomm issue RestComm#13. The String objects in question are never compared with ==, so it's safe to remove the intern() call.
deruelle
referenced
this issue
in mobius-software-ltd/corsac-sip
Jan 19, 2024
Fix right byte order in frame length encoding Conflicts: src/gov/nist/javax/sip/stack/WebSocketCodec.java
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
after profiling sessions a hotspot was identified in String.intern. Apparently the lookup cost is high
The text was updated successfully, but these errors were encountered: