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

Find good defaults for reduction parameters #418

Open
Tracked by #339
tomwhite opened this issue Mar 11, 2024 · 0 comments
Open
Tracked by #339

Find good defaults for reduction parameters #418

tomwhite opened this issue Mar 11, 2024 · 0 comments

Comments

@tomwhite
Copy link
Member

There are a couple of parameters we can set:

  • split_every, which controls the number of blocks in each stage of tree reduce (defaults to 4, but set to 10 in the quadratic means benchmark)
  • max_total_num_input_blocks, which controls how many blocks can be read by one task when doing optimization (not enabled by default, but set to 40 in the quadratic means benchmark)

This comment discusses the trade off to optimize: #331 (comment)

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

No branches or pull requests

1 participant