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

Batching fast running processes in HPC jobs #4749

Closed
saulpierotti opened this issue Feb 16, 2024 · 3 comments · May be fixed by #3909
Closed

Batching fast running processes in HPC jobs #4749

saulpierotti opened this issue Feb 16, 2024 · 3 comments · May be fixed by #3909

Comments

@saulpierotti
Copy link

New feature

It would be useful to have the possibility to set a batching parameter for grouping fast-running processes within the same HPC scheduler job. My idea would be to have a bunch of instances of the same process run sequentially within a single scheduler job, so to avoid overwhelming the scheduler with many jobs.

I sometimes find myself with what logically should be a single process to be too fast executing to merit allocating a job on the cluster, and if I do I end up with more than one million jobs, hitting limits on the number of concurrent jobs that the cluster admin allows. I could batch within the process execution in some custom way, but this requires ad-hoc code refactoring and it is not very elegant (i.e. a for loop running what should be a single process on a batch of inputs).

I don't know how easy this would be to implement, but was wondering weather anyone would have a similar need or has an idea if this is feasible.

@robsyme
Copy link
Collaborator

robsyme commented Feb 16, 2024

This is a sensible request. It sounds very similar to the task batching being worked on in PR #3909. That work has not been finalized or merged yet, but would the features described there solve your problem?

@bentsherman bentsherman linked a pull request Feb 16, 2024 that will close this issue
@bentsherman
Copy link
Member

This will be addressed by #3909 , until then you can use this pattern which is essentially the custom solution you described. But I think we will try to merge the task batching PR sometime this year.

@saulpierotti
Copy link
Author

Thanks both for the replies, yes this is exactly what I was looking for.

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

Successfully merging a pull request may close this issue.

3 participants