You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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?
Comment?
The text was updated successfully, but these errors were encountered:
jamieb22
changed the title
20% higher CPU with Wildfly-OpenSSL
40% higher CPU with Wildfly-OpenSSL
Aug 2, 2018
jamieb22
changed the title
40% higher CPU with Wildfly-OpenSSL
20% higher CPU with Wildfly-OpenSSL
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.
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?
Comment?
The text was updated successfully, but these errors were encountered: