-
Notifications
You must be signed in to change notification settings - Fork 5.9k
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
UCP: Speed up parse slow-log when query slow_query #15371
Comments
/pick-up-challenge |
@yzwqf the issue should be fixed and I noticed that you have 150 points in this repo, the medium level tasks required at least 200 points before picking up. |
it didn't make sense, would u please check #15021, #15036, #15401, #15031. |
/pick-up-challenge |
@yzwqf pick up issue success |
/give-up-challenge |
@yzwqf give up issue success |
/pick-up-challenge |
@yufeiminds don't have enough score, pick up failed Progress |
Alkaid will fix it this week :) |
* speed up the slow log query * speed up slow log query * change the MaxRow num * change channel location * correct * fix some bug * fix error situation * change ctx.Done() location * update * Update main.go * change func name * fix the len(rows)=0 bug * remove else * update slow_query_test * update slow_query_test.go * update slow_query_test.go * update slow_query_test.go * append offset var * fix bug * add notes * remove fmt * remove notes * remove notes * update * update * version back * update offset * update * use len(log)==0 to check * update * update offset struct * update offset * defer recover * update slow_query_test * update offset * remove fmt.print * check error first * update panic situation * update failpoint test * update failpoint test * update panic test * test * test * update test * update failpoint name * test * update slow_query.go * check err * Code specification * remove pointer * update getLineIndex func * update setFieldValue func * debug * update func name Co-authored-by: crazycs <[email protected]> Co-authored-by: ti-srebot <[email protected]>
Signed-off-by: ti-srebot <[email protected]> Signed-off-by: jyz0309 <[email protected]>
Description
After Issue #15354 laster, I found the performance improvement is not significant. The Read slow log file and parse process are slow.
So, we still need to speed up it.
Score
Use a bench test to judge the score, the bench test should in the below situation:
select count(*) from information_schema.slow_query
slow-log.log
file is 300M.Below is the score:
......
At least has 2x performance improvement, the max score is 1000.
Mentor(s)
Contact the mentors: #tidb-challenge-program channel in TiDB Community Slack Workspace
Recommended Skills
Learning Materials
slowQueryRetriever
search in TiDB code to see related implemention code.The text was updated successfully, but these errors were encountered: