N8n Regular mode concurrency control

Hi, i’m still in the learning process of using n8n. Currently i’m using a single n8n docker instance with 2 other users. i’ve done some search in the forum related to ‘concurrency’ for regular mode but still a bit blurry. Based on this doc Concurrency control | n8n Docs
I’m running n8n on regular mode.

Few questions:

  1. will this works on regular mode N8N_CONCURRENCY_PRODUCTION_LIMIT? Default its no limit on concurrency right?
  2. If no.1 above applicable for regular mode, if i set this parameter to like 20, the docs above says excess execution will be put in queue. So is this ‘queue’ is the same with the Queue mode? or I can still use queue in regular mode?
  3. If i can use queue in regular mode, should i also setup redis & redis parameter for the queue function to work on regular mode?

A bit confused…
Thanks

Information on your n8n setup

  • n8n version: 1.65.2
  • Database (default: SQLite): postgres
  • n8n EXECUTIONS_PROCESS setting (default: own, main): regular
  • Running n8n via (Docker, npm, n8n cloud, desktop app): docker
  • Operating system: arm64 ubuntu 20

You’re correct on Point 1 but i’m not sure about point 2. If you mean this part…

-from the doc
Use this to control how many production executions run concurrently, and queue up any concurrent production executions over the limit.

That is not the same as the queue mode imho.

Especially if take the comparison at the end of the doc into consideration.

from the doc
Concurrency control in queue mode is a separate mechanism from concurrency control in regular mode, but the environment variable N8N_CONCURRENCY_PRODUCTION_LIMIT controls both of them.

Unfortunately, i can’t tell you if redis is useful or necessary for your use case.

i know that redis is needed if i’m using queue mode setup. But since currently i’m on regular mode without redis & no concurrency limit, need some clarification whether i need to have redis + its QUEUE_BULL_REDIS_ parameter set up, if I want to limit the concurrency using N8N_CONCURRENCY_PRODUCTION_LIMIT

or maybe on regular mode, it has it’s own queue system without further config…

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.