Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

Single threaded in production #163

Closed
singpolyma opened this issue Feb 27, 2022 · 2 comments
Closed

Single threaded in production #163

singpolyma opened this issue Feb 27, 2022 · 2 comments

Comments

@singpolyma
Copy link

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?

@ioquatix
Copy link
Member

How many processor cores do you have on the instance and do you want to use them all?

@singpolyma
Copy link
Author

I'm aware that a single ruby process won't use multiple cores, but our webapps are generally I/O bound not CPU bound so that's never been a concern.

@socketry socketry locked and limited conversation to collaborators Feb 28, 2022
@ioquatix ioquatix converted this issue into discussion #165 Feb 28, 2022

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants