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

What's the impact of not running with Websockets #11

Open
adamgins opened this issue Feb 9, 2015 · 3 comments
Open

What's the impact of not running with Websockets #11

adamgins opened this issue Feb 9, 2015 · 3 comments

Comments

@adamgins
Copy link

adamgins commented Feb 9, 2015

@arunoda this sounds really interesting. I noticed that you are not running with Websockets. Anyway, I was wondering if you have any high-level guidance on what sort of performance impact could we expect on falling back to HTTP (vs TCP/Websockets), please?

@arunoda
Copy link
Member

arunoda commented Feb 9, 2015

We are not running with WS because of the SSL. We use Cloudflare for SSL and they don't support WS yet. So, we turned off WS.

It's a bit slower than WS for realtime stuff. But for Kadira, we found it's okay to turn off WS. There was not much latency issues.

And cluster works well with this situation too. Actually, it doesn't differentiate.

@adamgins
Copy link
Author

adamgins commented Feb 9, 2015

Thanks. Any rule of thumb/rough guide on what over head HTTP would put on your system vs websockets?

@arunoda
Copy link
Member

arunoda commented Feb 9, 2015

From the server perspective, it won't does anything different. (We haven't done any test yet).
But I've seen it reduces the server load for one of my friend. His app is being used in places where connection is very poor and WS is not available much.

So, WS gets re-connected everytime. That re-subscribe everything. But once he turned off WS, this issue was not there and server load gets reduced.

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

2 participants