-
-
Notifications
You must be signed in to change notification settings - Fork 576
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
Centrifugo release #1
Comments
Hello:) Just released all the things I've done, Centrifugo 0.1.0 is the first release, Note though, that at work we still use Centrifuge in production and will migrate to Centrifugo in several weeks - we are planning to see how it behaves - is it stable enough or not. |
hi,
So the battle between more memory vs more cores? |
Thanks @thedeadofblackfire for your question i want to ask the same. Iam also not familiar with Go language but if it make performance good why not. |
@thedeadofblackfire, to be fair I don't know which of servers better. I used a benchmark tool with up to 10k connections, but I did not try to connect more than 10k clients. And I don't see much sense in this - depending on application there will be different amount of clients, channels, messages per second - all of these need additional CPU and memory – so the way to decide when resource limit of one server reached - CPU and memory usage monitoring. |
Thanks for your reply. I think more memory is the best deal for now. Yep agree, 10 000 max connections simultaneous is already a solid base. I'm not yet at the beginning of the development phase about a medical chat platform. i like centrifuge & now centrifugo compared to pusher.com (price ^^). I try to make some projections of Use. The production phase will not be for the next months but i will try to use your benchmark on the servers to play with it (monitoring by newrelic). |
Ok, thanks, I am here and looking forward for your results. If you need any help – feel free to ask |
We finally replaced Centrifuge with Centrifugo in production 2 days ago. As we did this - we found problem with Redis engine resulting it message lost. That problem with Redis engine already fixed in version 0.2.3 Yesterday everything worked fine with updated code. Will see how it behaves. |
So I think Centrifugo is pretty stable at moment. In our project it works without any downtime since my last message. If you use Centrifugo please write me a message here or via email about your use case. |
I confirme that il is working on production without any downtime since 3 Le jeudi 24 septembre 2015, Alexandr Emelin notifications@github.com a
|
Closing this as Centrifugo > 1.0 already out🍾 |
Hi, Iam waiting the release. It is released or still in beta test ?
The text was updated successfully, but these errors were encountered: