Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enable optional Parallel runs #31

Open
sledigabel opened this issue Apr 27, 2021 · 2 comments
Open

Enable optional Parallel runs #31

sledigabel opened this issue Apr 27, 2021 · 2 comments

Comments

@sledigabel
Copy link
Contributor

at the moment all prs commits etc are sequential.
For large numbers, adding parallel processing could improve the user experience by accelerating the feedback loop.

@rnorth
Copy link
Collaborator

rnorth commented Apr 28, 2021

Yeah, I can see this being useful!

I think we'd need to be careful about two areas: logging and load on SCM/CI systems.

With logging it's fairly obvious; we'd need to present the logs in a non-confusing way, which is harder when parallelism is introduced.

Re load on SCM/CI systems, I think we should probably think about which commands create which kinds of loads. e.g. create-prs is already an operation which can be heavy on shared CI systems. The other operations that interact with GitHub will create different pressures, which are unlikely to be spread well for people using GitHub Enterprise.

The foreach command seems like an obvious candidate for parallelism without any surprise load concerns, though. We'd just need to think about the others!

@rnorth
Copy link
Collaborator

rnorth commented May 24, 2023

Doing #7 would help with this one.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants