[CHEETAH] Optimize the MulAA communication. #850
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Previous impl realizes the MulAA via two OLEs for computing two terms x0*y1 and x1*y0. This will introduce a larger communication overhead. We switch to another strategy by computing the sum x0*y1+x1*y0 homomorphically. To further utilize the CPU resources, we split a long vector into two subtasks and to let Rank0 and Rank1 to handle each half.
anakinxc
approved these changes
Sep 12, 2024
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Previous impl realizes the MulAA via two OLEs for computing two terms x0y1 and x1y0. This will introduce a larger communication overhead.
We switch to another strategy by computing the sum x0y1+x1y0 homomorphically. To further utilize the CPU resources, we split a long vector into two subtasks and to let Rank0 and Rank1 to handle each half.
Pull Request
What problem does this PR solve?
Issue Number: Fixed #
Possible side effects?
Performance:
Backward compatibility: