-
Notifications
You must be signed in to change notification settings - Fork 13
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
Default chunk_size and cores to ppj #79
Comments
Er, to be clear, setting |
Yes, definitely agree. Sidenote: do we handle infinite chunk size yet? I think we said if chunks are "0" we allow arbitrarily large chunks? |
Gabe, can you have a look at this fix and let me know what you think. |
This fix up looks okay to me, other than to generalize the default class a bit further if possible. |
We could generalize but then there might be too much metaprogramming black magic. I'll have a think about it this evening.
|
Lets handle this via #85 |
Back in issue #49 we discussed having chunk size defaulting to the ppj, but we lost track of that issue so I'm filing this.
I'm thinking it the logic should be: unless overridden in the environment or command-line,
-c
and-j
both default to--ppj
. That way, you default to running as many commands in parallel in a job as you have processors allocated, and the user only needs to change one option,--ppj
, if they want to scale that up or down.The text was updated successfully, but these errors were encountered: