-
Notifications
You must be signed in to change notification settings - Fork 4.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
support elastic-agent-shipper in diskqueue #32258
Conversation
f4910f9
to
d84e9d3
Compare
d84e9d3
to
0c384c8
Compare
Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane) |
I tried running Is this expected? How long does generating the benchmarks usually take? |
Co-authored-by: Tiago Queiroz <[email protected]>
Co-authored-by: Tiago Queiroz <[email protected]>
Co-authored-by: Tiago Queiroz <[email protected]>
Co-authored-by: Tiago Queiroz <[email protected]>
Co-authored-by: Tiago Queiroz <[email protected]>
Co-authored-by: Craig MacKenzie <[email protected]>
On my MBP it takes ~40 seconds before I see any output. If I add On my machine it takes ~40 minutes for the command line you used to run. I can look at reducing number of events, one thousand events was too small, it gives variances of 20%. One million has low variance 0-2% but it does take a long time. |
I had initially thought of implementing this by supporting configurable serialization as in elastic/elastic-agent-shipper#41, so the shipper could just add a callback for whatever we end up needing... but I think your way is good for now, since full generality would raise more complicated questions and we might not end up needing it. One question / concern about this approach: I still have the hope that (once all the glue is in place) our |
Haven't done it yet, but I think extending to support already encoded events would be straightforward. I think we would need:
|
100k events run quite fast o my X1 Extreme.
One little thing, the command to run the benchmark in the PR description needs to be updated to match the 100k functions. We can also use
|
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.
Come minor details about the tests.
Co-authored-by: Tiago Queiroz <[email protected]>
Co-authored-by: Tiago Queiroz <[email protected]>
:-) newer CPU, faster SSD & and a more efficient I/O scheduler will do that. It was
added |
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.
looks good!
* support elastic-agent-shipper in diskqueue Co-authored-by: Tiago Queiroz <[email protected]> Co-authored-by: Craig MacKenzie <[email protected]>
What does this PR do?
Adds support for elastic-agent-shipper as a client of diskqueue. Specifically
Why is it important?
Necessary for elastic-agent-shipper to use diskqueue
Checklist
CHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.How to test this PR locally
Related issues