Skip to content

云端并发性#

¥Cloud concurrency

Only for n8n Cloud

本文档讨论了 n8n Cloud 中的并发性。阅读 自托管 n8n 并发控制 了解自托管 n8n 实例的并发性。

¥This document discusses concurrency in n8n Cloud. Read self-hosted n8n concurrency control to learn how concurrency works with self-hosted n8n instances.

过多的并发执行会导致性能下降和无响应。为了避免此问题并提高实例稳定性，n8n 会在常规模式下为生产环境执行设置并发限制。

¥Too many concurrent executions can cause performance degradation and unresponsiveness. To prevent this and improve instance stability, n8n sets concurrency limits for production executions in regular mode.

超出限制队列的任何执行操作，将稍后处理。这些执行操作会一直保留在队列中，直到并发容量释放，然后按先进先出 (FIFO) 的顺序处理。

¥Any executions beyond the limits queue for later processing. These executions remain in the queue until concurrency capacity frees up, and are then processed in FIFO order.

并发限制#

¥Concurrency limits

n8n 根据云实例的计划限制其并发执行次数。有关详细信息，请联系 定价。

¥n8n limits the number of concurrent executions for Cloud instances according to their plan. Refer to Pricing for details.

你可以在项目或工作流的“执行”选项卡顶部查看活动执行次数和计划的并发限制。

¥You can view the number of active executions and your plan's concurrency limit at the top of a project's or workflow's executions tab.

详细信息#

¥Details

关于并发，需要注意的其他一些细节：

¥Some other details about concurrency to keep in mind:

  • 并发控制仅适用于生产环境执行：由 webhook 或触发器节点启动的操作。它不适用于其他类型的操作，例如手动执行、子工作流执行或错误执行。

¥Concurrency control applies only to production executions: those started from a webhook or trigger node. It doesn't apply to any other kinds, such as manual executions, sub-workflow executions, or error executions.

  • 测试评估 不计入并发限制。你的测试评估并发限制与你套餐的常规并发限制相同，但彼此独立。

¥Test evaluations don't count towards concurrency limits. Your test evaluation concurrency limit is equal to, but separate from, your plan's regular concurrency limit.

  • 无法重试已排队的执行。取消或删除已排队的执行也会将其从队列中移除。

¥You can't retry queued executions. Cancelling or deleting a queued execution also removes it from the queue.

  • 实例启动时，n8n 会恢复已排队的执行任务，直至达到并发限制，并将剩余任务重新排队。

¥On instance startup, n8n resumes queued executions up to the concurrency limit and re-enqueues the rest.

与队列模式比较#

¥Comparison to queue mode

Feature availability

队列模式适用于云企业版计划。至启用它，联系 n8n。

¥Queue mode is available for Cloud Enterprise plans. To enable it, contact n8n.

队列模式下的并发控制与常规模式下的并发控制是不同的机制。在队列模式下，并发设置决定了每个工作进程可以并行运行多少个作业。在常规模式下，并发限制适用于整个实例。

¥Concurrency in queue mode is a separate mechanism from concurrency in regular mode. In queue mode, the concurrency settings determine how many jobs each worker can run in parallel. In regular mode, concurrency limits apply to the entire instance.