Skip to content

Communicate min block len only on first block in section - #622

Merged
yousefmoazzam merged 2 commits into
mainfrom
min-block-len-communication
Sep 11, 2025
Merged

yousefmoazzam merged 2 commits into
mainfrom
min-block-len-communication

Conversation

@dkazanc

@dkazanc dkazanc commented Sep 1, 2025 •

Copy link
Copy Markdown
Collaborator

Looks like a PR needed for this after the confirmation on the improvement made by Radway.
Fixes #ISSUE

Checklist

  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • I have made corresponding changes to the documentation

@yousefmoazzam

Copy link
Copy Markdown
Collaborator

Cool, I'll have a look if a test can be added to guard against a regression, I think it may not be too difficult to do.

@yousefmoazzam
yousefmoazzam force-pushed the min-block-len-communication branch 2 times, most recently from 62b468b to 097ac25 Compare September 2, 2025 15:01
The reason that checking if the reduce method on the communicator was
called is used as a proxy for checking if the minimum block length was
communicated is because the former can be done with one MPI process (via
mocking the size of the communicator). On the other hand, checking
directly if the minimum block length was communicated or not would
require running two or more processes, which is less convenient in unit
tests.
@yousefmoazzam
yousefmoazzam force-pushed the min-block-len-communication branch from 097ac25 to 540380f Compare September 11, 2025 12:38
@yousefmoazzam
yousefmoazzam merged commit 0296642 into main Sep 11, 2025
8 of 9 checks passed
@yousefmoazzam
yousefmoazzam deleted the min-block-len-communication branch September 11, 2025 13:26
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 this pull request may close these issues.

2 participants