You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are currently used to using thin via rackup in production for single-threaded but evented (and thus concurrent) request handling with eventmachine.
We are curious about leaving eventmachine for ruby3. The documentation says that using falcon with rackup is not recommended, but is this just because it will be single-threaded? Since our code will all be async, that seems like not such a big deal and probably we can expect performance similar to thin when used in this way?
The text was updated successfully, but these errors were encountered:
We are currently used to using
thin
viarackup
in production for single-threaded but evented (and thus concurrent) request handling with eventmachine.We are curious about leaving eventmachine for ruby3. The documentation says that using falcon with
rackup
is not recommended, but is this just because it will be single-threaded? Since our code will all be async, that seems like not such a big deal and probably we can expect performance similar to thin when used in this way?The text was updated successfully, but these errors were encountered: