Hi!
I have n8n running on AWS, and when I receive multiple requests at the same time (or within a few seconds), cpu usage goes through the roof and eventually the requests fail with code 522 - connection timed out. Is there anything I can do to avoid this?
Thanks for your help!
@cdesseaux the posts below should clarify. If not, simply get back to me.
Should be normally more than enough.
Not sure if I understand correctly. Are you calling a webhook for every request you get or do you have batch task? Or both?
If you receive a lot of requests, especially a lot of requests in parallel, it is probably best if you tell n8n to run all workflow executions in the main process. That is not just way faster it saves a lot of resources.
You can do that by setting:
export EXECUTIONS_PROCESS=main
Here the documentation:
Hello all,
I’ve upgraded from 0.94 to 0.114 and I am a bit confused about the worker processes that are started with n8n worker…
I did read on the basics through Scaling n8n | n8n Docs but I’m not clear on how to configure them.
is there any general figures on how many concurrency there should or shouldn’t be?
and on another note; is
5* “n8n worker 10” processes
the same as
1* “n8n worker 50” process?
Hi,
how can I change the settings to ‘export EXECUTIONS_PROCESS=main’?
I can access my server via ssh, but i seem to only have access the docker-compose file in there.
sorry if this is really basic stuff, I’m kind of new at this.
Thanks for your help!
You can add another line underneath environment in your docker-compose.yml file:
The line would be:
- EXECUTIONS_PROCESS=main
