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.

Sign up for GitHub

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

Jump to bottom

Feature Request: configurable SSLEngine #226

Open
lpage30 opened this issue Mar 26, 2015 · 1 comment
Open

Feature Request: configurable SSLEngine #226

lpage30 opened this issue Mar 26, 2015 · 1 comment
Labels
improvement

Comments

@lpage30
Copy link
Contributor

lpage30 commented Mar 26, 2015

We are using sio v. 1.7.7. With ~2000 websocket clients connecting we see CPU go way high and latency for connection way up (this is in a load test environment).
We can 'blur' the connections from the client but after some looking around, we were thinking 'wouldn't it be great if we could use the stock netty OpenSSL (comes with 4.0.25) or twitter OpenSSL for SSLEngine instead of the stock JDK'.

There are performance gains that could be had if other engines could be used.
Thanks.
@mrniko
Copy link
Owner

mrniko commented Jun 22, 2015

This feature also fixes this one #234
@mrniko mrniko added this to the 1.7.8 milestone Jun 22, 2015
@mrniko mrniko modified the milestone: 1.7.8 Nov 30, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
improvement
2 participants
@mrniko @lpage30