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

Should we fall back to serial execution for nchunks=1 and chunksize>length(input)? #72

Open
carstenbauer opened this issue Mar 7, 2024 · 1 comment
Labels
question Further information is requested

Comments

@carstenbauer
Copy link
Member

In both cases, we end up with a single chunk and already now run effectively serially. However, the difference to SerialScheduler is that we

  • run a different code path and thus
  • still create and spawn a (single) task which might run on a non-main thread.
@carstenbauer carstenbauer added the question Further information is requested label Mar 7, 2024
@arnaud-ma
Copy link
Contributor

Maybe having a new argument like single_chunk_mode = :serial or a boolean one serial1chunk = true can be a good idea. I think this is related to #114. One of the reasons for having minchunksize is to have (almost) no overhead when minchunksize > length(input).

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

No branches or pull requests

2 participants