starred/act

Fork 0

mirror of https://github.com/nektos/act.git synced 2026-04-26 01:15:51 +03:00

[GH-ISSUE #2732] Increase parallel job limit #1234

New issue

Open

opened 2026-03-01 21:49:51 +03:00 by kerem · 2 comments

kerem commented

2026-03-01 21:49:51 +03:00

Owner

Originally created by @ncaq on GitHub (Apr 14, 2025).
Original GitHub issue: https://github.com/nektos/act/issues/2732

Act version

act version 0.2.76

Feature description

I would like to request an enhancement to allow act to run jobs in greater parallelism by default. I primarily contribute by submitting pull requests to various GitHub repositories maintained by others. Since GitHub Actions require maintainer approval before running CI, I frequently use act for local testing. When utilizing matrix jobs to test across multiple environments, the hard limit of 4 concurrent jobs causes slower execution times.

I understand that this limit was intentionally introduced (see fix: add simple concurrency limit by catthehacker · Pull Request #823 · nektos/act). Although it is possible to control the concurrency via file configuration, I often work on many OSS projects and make temporary patches without the intention of adding or committing non-standard configuration files. Having to modify files every time not only feels cumbersome, but there is also a risk of accidentally committing these settings.

I propose that when sufficient CPU and memory resources are available, act should automatically allow a higher number of parallel jobs without requiring manual file-based configuration changes. This improvement would greatly streamline local testing workflows by significantly reducing the total test execution time when running multiple jobs concurrently.

Originally created by @ncaq on GitHub (Apr 14, 2025). Original GitHub issue: https://github.com/nektos/act/issues/2732 ### Act version act version 0.2.76 ### Feature description I would like to request an enhancement to allow `act` to run jobs in greater parallelism by default. I primarily contribute by submitting pull requests to various GitHub repositories maintained by others. Since GitHub Actions require maintainer approval before running CI, I frequently use `act` for local testing. When utilizing matrix jobs to test across multiple environments, the hard limit of 4 concurrent jobs causes slower execution times. I understand that this limit was intentionally introduced (see [fix: add simple concurrency limit by catthehacker · Pull Request #823 · nektos/act](https://github.com/nektos/act/pull/823)). Although it is possible to control the concurrency via file configuration, I often work on many OSS projects and make temporary patches without the intention of adding or committing non-standard configuration files. Having to modify files every time not only feels cumbersome, but there is also a risk of accidentally committing these settings. I propose that when sufficient CPU and memory resources are available, `act` should automatically allow a higher number of parallel jobs without requiring manual file-based configuration changes. This improvement would greatly streamline local testing workflows by significantly reducing the total test execution time when running multiple jobs concurrently.

kerem added the

kind/feature-request

label

2026-03-01 21:49:51 +03:00

kerem commented

2026-03-01 21:49:51 +03:00

Author

Owner

@ncaq commented on GitHub (Apr 14, 2025):

While the source code suggests that excessive parallelism isn't necessary, I've encountered practical limitations with the current settings.

When working with repositories that have extensive matrix patterns like awakesecurity/proto3-suite: Haskell Protobuf Implementation, I found that the default 4-way parallelism significantly underutilizes my Ryzen 9950X3D's resources. This results in slower local execution times than what my hardware is capable of.

@ncaq commented on GitHub (Apr 14, 2025): While the source code suggests that excessive parallelism isn't necessary, I've encountered practical limitations with the current settings. When working with repositories that have extensive matrix patterns like [awakesecurity/proto3-suite: Haskell Protobuf Implementation](https://github.com/awakesecurity/proto3-suite), I found that the default 4-way parallelism significantly underutilizes my Ryzen 9950X3D's resources. This results in slower local execution times than what my hardware is capable of.

kerem commented

2026-03-01 21:49:52 +03:00

Author

Owner

@qoomon commented on GitHub (Jun 6, 2025):

should be fixed by https://github.com/nektos/act/pull/2762

@qoomon commented on GitHub (Jun 6, 2025): should be fixed by https://github.com/nektos/act/pull/2762

kerem referenced this issue

2026-03-01 21:52:58 +03:00

[PR #1234] [MERGED] build(deps): bump github.com/rhysd/actionlint from 1.6.13 to 1.6.14 #1855

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/act#1234

No description provided.

Rows
Columns