-
Notifications
You must be signed in to change notification settings - Fork 442
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
[O11y][MySQL] Rally benchmark mysql.error
#8957
Conversation
🚀 Benchmarks reportPackage
|
Data stream | Previous EPS | New EPS | Diff (%) | Result |
---|---|---|---|---|
error |
12987.01 | 4444.44 | -8542.57 (-65.78%) | 💔 |
slowlog |
18518.52 | 9615.38 | -8903.14 (-48.08%) | 💔 |
To see the full report comment with /test benchmark fullreport
"version": "8.8.0", | ||
"snapshot": false | ||
}, | ||
"message": "{{$timestamp.Format "2006-01-02 15:04:05"}} {{ $thread_id }} [{{ $log_level }}] {{ generate "message" }}", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Given that we need to improve the message generated in logs as per this, I couldn't find any fixed format over the error logs. Please refer here in case.
- mysqld_safe Starting mysqld daemon with databases from /usr/local/var/mysql
- InnoDB: The InnoDB memory heap is disabled
- InnoDB: Mutexes and rw_locks use GCC atomic builtins
Should we go like generating an enum of these messages
which would have around 10 to 12 error logs?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i think having somethign more realistic would be good if it's not too much effort.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks. Provided the messages as per the log_level
. Please have a look
enum: ["Note", "Warning", "System", "ERROR"] | ||
- name: message | ||
type: text | ||
- name: thread_id |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
would we expect this to have such high cardinality in real life?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@tommyers-elastic Are you referring the range of values this field is generating? I agree that the values are not that high in the logs here. Let me update this to maybe max value as 20-30.
… into mysql_benchmark_error
💚 Build Succeeded
History
cc @aliabbas-elastic |
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nice work - thanks!
Proposed commit message
error
data stream ofMySQL
Checklist
How to test this PR locally
Run this command from package root
elastic-package benchmark rally --benchmark error-benchmark -v
elastic-package benchmark stream --benchmark error-benchmark -v
Related issues
Screenshots