Skip to content
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

20% higher CPU with Wildfly-OpenSSL #51

Open
jamieb22 opened this issue Aug 2, 2018 · 0 comments
Open

20% higher CPU with Wildfly-OpenSSL #51

jamieb22 opened this issue Aug 2, 2018 · 0 comments

Comments

@jamieb22
Copy link

jamieb22 commented Aug 2, 2018

Our app receives and establishes a large amount of TLS connections per minute. I noticed that CPU utilization is about 20% higher with Wildfly-OpenSSL enabled as compared to standard JSSE activated (incidentally, in this environment, our app is running inside a virtual machine with 16 CPU cores assigned). I'm not entirely clear on why there would be such a huge difference. Tomorrow, I'll run in a profiler and see what's up.

cpu

Interestingly, no. packets and bytes transferred is significantly lower with Wildfly-OpenSSL enabled. At first I thought, that after installing Wildfly that some TLS connections where somehow being rejected, but alas I cannot not confirm this. Its baffling because I remain unconvinced that differences of this magnitude could be attributed to differences in implementation between OpenSSL and JSSE. Could it be difference in session handling option?

networkpackets

networkbytes

Comment?

@jamieb22 jamieb22 changed the title 20% higher CPU with Wildfly-OpenSSL 40% higher CPU with Wildfly-OpenSSL Aug 2, 2018
@jamieb22 jamieb22 changed the title 40% higher CPU with Wildfly-OpenSSL 20% higher CPU with Wildfly-OpenSSL Aug 2, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant