[Feature Request] Allow configurable Parallel Block concurrency limit beyond 20

Aberta
  • Algo errado?
#4,903 3 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

@sahooarnav2007-gif já está trabalhando nisso.

Desde 26/10/2026.

Avaliação

Dificuldade
5/5
Tempo estimado
Mais de uma semana
Facilidade para iniciantes
35/100
Tipo de issue
Funcionalidade
Clareza
Razoavelmente clara
Status de atividade
Pouca atividade
Stack de tecnologia
typescript
Domínio
backend

Direção de pesquisa

Start by locating the Parallel Block implementation and reading how its current batch limit is applied. Then trace how concurrency is handled for nested blocks and different task types. Done means a chosen approach lets users run larger parallel workloads while making the concurrency limit clear and configurable or appropriately raised.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

feature

Feature Request: Increase or remove the hard cap on Parallel Block batch size (currently limited to 20)
Current Behavior
The Parallel Block currently enforces a maximum batch size of 20 concurrent executions. When the number of items exceeds this limit, the block automatically falls back to serial batching — processing 20 at a time and waiting for each batch to complete before starting the next.
Problem
This hard cap of 20 is unnecessarily restrictive for use cases that do not involve LLM calls or external API rate limits. For example:

  • Processing 50–100 items through pure compute tasks (data transformation, formatting, rule-based routing, math operations)
  • Nested Parallel Blocks (Parallel inside Parallel) where the outer block fans out to N branches and each inner block also runs M tasks concurrently — the 20-limit applies at every level independently, causing compounding serial batching even when no rate-limited resources are involved
  • Workflows where all parallel tasks are self-contained Function blocks with zero external I/O

In these scenarios, the 20-item cap forces unnecessary sequential waiting, increasing total execution time without any technical justification.
Proposed Solution
Please consider one or more of the following approaches:

  1. Raise the default cap from 20 to at least 50 or 100
  2. Allow user-configurable concurrency limit — let users set their own maxConcurrency value per Parallel Block (e.g. 1–200), so they can tune it based on their actual workload and resource constraints
  3. Distinguish between LLM and non-LLM tasks — apply a conservative default only when the inner blocks contain Agent/LLM nodes, and use a higher (or unlimited) default for pure compute tasks
    Use Case Example
    With a fixed cap of 20, this degrades into multiple serial batches even though the hardware and platform have no real constraint preventing full concurrency.
    Expected Behavior
    Users should be able to configure maxConcurrency freely per Parallel Block, or at minimum have a significantly higher ceiling (50–100), so that non-LLM parallel workloads can execute at full speed without artificial bottlenecks.
    Why This Matters
    Workflow automation platforms derive much of their value from true parallelism. Capping concurrency at 20 — regardless of workload type — undermines this core value proposition for power users who need high-throughput, non-LLM parallel processing.
    Thank you for considering this improvement!
Linguagem predominante
TypeScript
Estrelas
29.8k
Forks
3.9k
Merge médio
1h 44min
PRs com merge (30d)
841

Preparar o ambiente

Este projeto não oferece contêiner de desenvolvimento, Dockerfile nem guia de contribuição, então a configuração fica por sua conta: comece pelo README e veja nosso guia da primeira contribuição para os passos gerais.

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de simstudioai/sim

Todas as issues de simstudioai/sim

Issues semelhantes

Mais issues de TypeScript

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.