Daniel (dB.) Doubrovkine
Daniel (dB.) Doubrovkine
Were you using celluloid before or faye-websocket?
I would appreciate if someone could get to the bottom of this with celluloid. Good project to dive deep!
> +1! Have also been experiencing this behavior after switching to celluloid-io. > > If I have uninstalled `celluloid-io` and installed `async-websocket` again, do I still need to set `CONCURRENCY=async-websocket`...
I wish someone actually fixed the celluloid bug. Or maybe someone can do the work to deprecate celluloid usage everywhere and hardcode async-websocket?
I've labeled this as a feature request, we want hotswap/reloading. No idea how to implement it, so PRs welcome.
Likely related, https://github.com/slack-ruby/slack-ruby-client/issues/208
Oh so you have a bot that's online just fine that's leaking memory? That's not good :) I would find a way to dump the difference and see what objects...
I think https://stackoverflow.com/questions/20385767/finding-the-cause-of-a-memory-leak-in-ruby has pretty good information overall. I would aggressively `GC.collect` somewhere in the code/library and start dumping what's allocated to see a pattern.
This has been talked about in https://github.com/dblock/slack-gamebot/issues/81, which is entirely based on this code. I think you can do low thousands today, however there're two known issues, possibly not that...
The problem with this is that a service needs to expose an endpoint for registration. When that happens you need to start a bot instance. I guess it's ok that...