Added cmd_chain_throught and cmd_chain_latency tests to VE2#27
Merged
Conversation
Signed-off-by: Manoj Takasi <Manoj.Takasi@amd.com>
This file contains hidden or 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
2 participants
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.
Added cmd_chain_throught and cmd_chain_latency tests to VE2
Due to the HSA queue dependency, which is currently hardcoded to 32, we are unable to submit more than 32 commands simultaneously. For now, I’ve created cmd_chain_latency.json with 32 instances. Once the VE2 driver is fixed, I will update recipe.json with more instances to obtain better average latency and throughput values.