Fix calculation of geomean in TPROC-H #504
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
Signed-off-by: Igor Konopko <igor.j.konopko@intel.com>
sm-shaw
approved these changes
Feb 2, 2023
memmertoIBM
approved these changes
Feb 2, 2023
abondvt89
approved these changes
Feb 9, 2023
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.
Query 15 in TPROC-H is a multi-statement query, which consists of two parts: creating the view and querying that view. Due to that it is handled using separate code then all the other queries. Currently, the execution time of query 15 is not calculated as a part of geometric mean value, which is the metric for that test.
This patch fixes that to include query execution time in geometric mean metric. Creating/dropping the view is still not taken into that calculation, so no changes here.
Signed-off-by: Igor Konopko igor.j.konopko@intel.com