V1
Joined 15 years ago
Karma
128
Submissions
36
Member since
Apr 11
Recent submissions
Comment · 12 years ago
To bad that networks/proxies usually block websocket connections causing this solution to fail.
Comment · 12 years ago
You could also just use Primus which exposes a Stream compatible wrapper by default for the client and server.
https://github.com/primus/primus
(Primus uses engine.io,sockjs,browserchannel,websockets internally so you're no longer locked into a specific framework)
Comment · 13 years ago
Even Google is using it ;)
Comment · 13 years ago
Thanks for you feedback, I did do some testing with multiple backends (4 different servers) but it didn't show any substantial changes. I'll see if I can do some in depth in a while.
Comment · 13 years ago
I'll be more then happy to see if my configurations can be tweaked. And I was surprised as well, but it seems that it always boils down to the configuration files a small change can sometimes yield great results as seen with a specifying ciphers for SSL.
Comment · 13 years ago
It's not a `local` server. The proxy, websocket server and the benchmark utility are all on different servers.
Comment · 13 years ago
The `http-server-close` option did not change anything. But by adding the ciphers it was able to squeeze out the same performance as Nginx. I'll update the tests accordingly. Thanks for the heads up!.
Comment · 13 years ago
hipache is build on top of http-proxy. That's why I haven't included it in the tests. They have seem to have switched to a fork of http-proxy but there aren't big (if any) performance modifications as far as i've seen from the commits.
Comment · 13 years ago
I'll re-run the test with the advised changes and see if the performance improves.
Comment · 13 years ago
Because we people obviously don't have a datacenter in our own basement. And the common mistake people make when benchmarking is running the servers on their own machine and then use the same machine to benchmark the server it's running.
You need to have multiple (powerful) machines for this. And also, spinning up machines in the cloud is quite easy to do and allows people to reproduce the same test results because you have access to exactly the same environment.
Comment · 13 years ago
Are you referring to the cipher verification? I used:
openssl s_client -host localhost -port 8082
See https://gist.github.com/3rd-Eden/5345018 for the output of the openssl s_client for those ciphers. You'll see that `cipher : RC4-SHA` is used here. Which is one of the fastest if not the fastest cipher available.