[CBRD-24584] Improved to minimize the impact of query execution speed when setting sql_trace_slow #4002
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
… when setting sql_trace_slow
beyondykk9
requested review from
ctshim,
hgryoo,
hyunikn,
shparkcubrid and
youngjinj
ctshim
approved these changes
Dec 28, 2022
hyunikn
approved these changes
Dec 29, 2022
shparkcubrid
approved these changes
Jan 3, 2023
hgryoo
approved these changes
Jan 4, 2023
youngjinj
approved these changes
Jan 5, 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.
http://jira.cubrid.org/browse/CBRD-24584
When setting the sql_trace_slow value in cubrid.conf to a positive number other than -1, the query performance is highly affected compared to 9.x.
The reason for the increased impact on query performance compared to 9.x is that statdump information is calculated before starting a query and after finishing query execution.
Therefore, it is necessary to minimize the impact on query performance by improving it to calculate only the information necessary for setting sql_trace_slow.