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

Perf test and document # of max RTM connections and memory usage #114

Open
thbar opened this issue Oct 10, 2016 · 1 comment
Open

Perf test and document # of max RTM connections and memory usage #114

thbar opened this issue Oct 10, 2016 · 1 comment

Comments

@thbar
Copy link

thbar commented Oct 10, 2016

I'm only having a first look at slack-ruby-client and I wonder: typically, how many concurrent RTM connections are usually handled successfully without problems? Is it more in the 10, 100, 1000 range? Thanks!

(Note that I will do my homework, of course, yet I'm curious to hear about anyone with > 100 RTM connections setup).

@dblock
Copy link
Collaborator

dblock commented Oct 10, 2016

I have production services on https://www.playplay.io with many hundreds using https://github.com/slack-ruby/slack-ruby-bot-server which uses this library. The biggest issue becomes memory and startup time: ~1/3s to start (#87 needs fixing) and 1MB per connection.

This is generally a good question. Would love a paragraph in the README about this with some actual tests rather than anecdotal evidence.

@dblock dblock changed the title Largest tested number of RTM connections? Perf test and document # of max RTM connections and memory usage Oct 10, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants