|
Hi, Been starting to use Rage and I think it's great. One issue I encountered is that when I have a long request with the current configuration of Is there a reason Thanks |
Answered by
rsamoilov
Nov 14, 2025
Replies: 1 comment 2 replies
|
Hey Josh, Yes, Rage is purposefully single-threaded and quite similar to how Node.js works. There are a couple of reasons for this:
If your workflow involves CPU-bound tasks, you can use the multi-worker mode to run Rage in multiple processes: Rage.configure do
config.server.workers_count = -1 # run as many workers as there are CPU cores
endCan you share an example code snippet that blocks the webserver for you? |
2 replies
Answer selected by
joshdvir
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hey Josh,
Yes, Rage is purposefully single-threaded and quite similar to how Node.js works. There are a couple of reasons for this:
If your workflow involves CPU-bound tasks, you can use the multi-worker mode to run Rage in multiple processes: