-
Notifications
You must be signed in to change notification settings - Fork 456
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][System] Rally benchmark system.memory
#9296
Conversation
🚀 Benchmarks reportTo see the full report comment with |
@aliabbas-elastic Please add sample_event.json. |
Done. Please have a look |
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.
LGTM!
min: 8000000000 | ||
max: 9000000000 |
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.
How these ranges contribute to the benchmark? If I tune these parameters, will the result change?
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.
These ranges just provide you the liberty to set fields with realistic values. Like for example here the values are correlated with each other. If you see the system_memory_actual_used_bytes
ranges compared to this they would be lesser which will be the case in real environments as well. Modifying these wouldn't change the benchmarking stats.
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.
@@ -0,0 +1,35 @@ | |||
fields: | |||
- name: timestamp | |||
period: -60m |
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.
Why -
is prefixed?
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.
This is in reference to this doc
https://github.com/elastic/elastic-integration-corpus-generator-tool/blob/main/docs/fields-configuration.md#:~:text=generator%20will%20stop.-,period,-optional%20(date
It would always generate documents before time.Now()
so that the events would always be available in Last
duration in Discover
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.
Cool!
… into system_benchmark_memory
💚 Build Succeeded
History
cc @aliabbas-elastic |
Quality Gate passedKudos, no new issues were introduced! 0 New issues |
Proposed commit message
memory
data stream ofSystem
Sample Response
sample_event.json
Checklist
How to test this PR locally
Run this command from package root
elastic-package benchmark rally --benchmark memory-benchmark -v
elastic-package benchmark stream --benchmark memory-benchmark -v
Related issues
Screenshots