7 ms·
If you were IO bound you could have run many more rails processes. There's no reason to limit your self to one process per core. You can run many times that num
by jacobsenscott 6y ago
If you were IO bound you could have run many more rails processes. There's no reason to limit your self to one process per core. You can run many times that number of processes since they are all just waiting on IO.
- EdwardDiego 6y agoI'm sure the original commenter is loving all your 20/20 hindsight.
- coldtea 6y agoThe original commenter offered his story as an issue with Ruby preventing X. The 20/20 hindsight is not meant to retroactively solve their problem, it's mean as a counter-argument, that the problem was their design, not Ruby.
- Person5478 6y agoThe posters point is that Ruby has surprising concurrency semantics compared to other solutions.
- Evan__ 6y agoIt has the same concurrency semantics w/r/t IO as any other language that isn't using an event based runtime. If you wrote your app in C and used a single thread you'd have the exact same issue.