-
Notifications
You must be signed in to change notification settings - Fork 334
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
Parallelization of ConstProp compilation #3042
Merged
Merged
Changes from all commits
Commits
Show all changes
18 commits
Select commit
Hold shift + click to select a range
eb4a777
Parallelize compilation of ConstProp.
imaihal 74291c5
Add tentative implementation for parallelizing inner loop.
imaihal 2056cfb
Remove tentative implementation.
imaihal 96f98ce
Merge branch 'main' into constprop_parallel
imaihal a476c36
Merge branch 'main' into constprop_parallel
imaihal adf6ca9
Remove an argument for MLIRcontext in functionTransform().
imaihal abf14f9
Merge branch 'main' into constprop_parallel
imaihal 4ba7d33
Restore necessary MLIRContext.
imaihal f42244d
Remove mutex.
imaihal c0a39cc
Merge branch 'main' into constprop_parallel
imaihal ed3cc97
Add a threshold to run in parallel.
imaihal c96556c
Merge branch 'main' into constprop_parallel
imaihal 43dc668
Update threshold.
imaihal 76095b9
Add lit test.
imaihal 47792b6
Merge branch 'main' into constprop_parallel
imaihal b6f25e9
Update comments.
imaihal 8d17387
Update fetchBatch() for serial exec.
imaihal 099e9f3
Add measurement results as comments.
imaihal File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I also assume that the work up there assumes that there are
batch.size()
reductions that can all be done in parallel.Since we have for quantization "whole tensor" quantization, we have cases where we have only 1 reduction.
That can also be done in parallel. Say you have 1000 elements and 10 threads. Each thread process its own 100 numbers, and save its result in its location in an array of 10 partial sum. Then after the parallel region, just reduce these 10 values sequentially. You will still get a near 10x speedup.
Also, should we check if that if the
batch.size
is small, we may want to do things sequentially? It would probably be good in case we have a few very small tensors. You can easily print out the sizes on stderr for a few benchmarks and see if you have such cases.