Make the order of outputs the same as the order of inputs when using mii.pipeline
#384
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When doing batch inference using the "Non-Persistent Pipeline" method, i.e. using
mii.pipeline, the order of outputs is arbitrary, and has no correlation with the order of inputs. This becomes especially obvious when the generated outputs are of varying lengths and therefore finish at different times.In fact, printing the output if this line of code
uids_complete_order.append(uids_running.index(uid))would make it clear that it is incorrect, given that it outputs the same index multiple times.I have tested this PR on a single GPU.