--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-ta...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/263cc035-170e-4c45-b5d7-f047662c8416%40googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-ta...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/80cfa78d-a199-40a9-8654-0665943b7686%40googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rubyonrails-ta...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rubyonrails-talk/bdc5b160-efbe-4bba-9bc0-f3e889ed082d%40googlegroups.com.
I also asked the Puma guy.
They basiaclly said they receive this inquiry frequently, and they don't support it as they did not use it themselves.
https://github.com/puma/puma/issues/1895
I am still open for any pointers and suggestions. Maybe Puma guys just don't want to look deeply into it.
It is the Ruby community after all.
My default action now is to create multiple Puma instances (Not just adding a worker)
I wonder if there are other ways that did not incur burden on the operation team.