Skip to content

Conversation

@mauri870
Copy link
Member

@mauri870 mauri870 commented Sep 18, 2024

Proposed commit message

This benchmark uses a hardcoded Hello World response. In a real world scenario responses will range in size, specifically for _bulk responses. Updated the benchmark to consider different sizes when benchmarking this function.

go test -benchmem -run=^$ -tags integration,unit -bench ^BenchmarkExecHTTPRequest$ github.com/elastic/beats/v7/libbeat/esleg/eslegclient -v -count=1

goos: linux
goarch: amd64
pkg: github.com/elastic/beats/v7/libbeat/esleg/eslegclient
cpu: Intel(R) Xeon(R) CPU E5-2697A v4 @ 2.60GHz
BenchmarkExecHTTPRequest
BenchmarkExecHTTPRequest/size:_100
BenchmarkExecHTTPRequest/size:_100/unknown_length
BenchmarkExecHTTPRequest/size:_100/unknown_length-32              468573              2295 ns/op             976 B/op         10 allocs/op
BenchmarkExecHTTPRequest/size:_100/known_length
BenchmarkExecHTTPRequest/size:_100/known_length-32                479560              2313 ns/op             976 B/op         10 allocs/op
BenchmarkExecHTTPRequest/size:_10240
BenchmarkExecHTTPRequest/size:_10240/unknown_length
BenchmarkExecHTTPRequest/size:_10240/unknown_length-32            407080              2770 ns/op             976 B/op         10 allocs/op
BenchmarkExecHTTPRequest/size:_10240/known_length
BenchmarkExecHTTPRequest/size:_10240/known_length-32              400564              2773 ns/op             976 B/op         10 allocs/op
BenchmarkExecHTTPRequest/size:_102400
BenchmarkExecHTTPRequest/size:_102400/unknown_length
BenchmarkExecHTTPRequest/size:_102400/unknown_length-32            97029             10625 ns/op             977 B/op         10 allocs/op
BenchmarkExecHTTPRequest/size:_102400/known_length
BenchmarkExecHTTPRequest/size:_102400/known_length-32             110724             10744 ns/op             976 B/op         10 allocs/op
BenchmarkExecHTTPRequest/size:_1048576
BenchmarkExecHTTPRequest/size:_1048576/unknown_length
BenchmarkExecHTTPRequest/size:_1048576/unknown_length-32            4808            241032 ns/op            1194 B/op         10 allocs/op
BenchmarkExecHTTPRequest/size:_1048576/known_length
BenchmarkExecHTTPRequest/size:_1048576/known_length-32              4701            239657 ns/op            1199 B/op         10 allocs/op

Checklist

  • My code follows the style guidelines of this project
  • I have commented my code, particularly in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have made corresponding change to the default configuration files
  • I have added tests that prove my fix is effective or that my feature works
  • I have added an entry in CHANGELOG.next.asciidoc or CHANGELOG-developer.next.asciidoc.

Related issues

@mauri870 mauri870 added cleanup Team:Elastic-Agent-Data-Plane Label for the Agent Data Plane team labels Sep 18, 2024
@botelastic botelastic bot added needs_team Indicates that the issue/PR needs a Team:* label and removed needs_team Indicates that the issue/PR needs a Team:* label labels Sep 18, 2024
@mergify
Copy link
Contributor

mergify bot commented Sep 18, 2024

This pull request does not have a backport label.
If this is a bug or security fix, could you label this PR @mauri870? 🙏.
For such, you'll need to label your PR with:

  • The upcoming major version of the Elastic Stack
  • The upcoming minor version of the Elastic Stack (if you're not pushing a breaking change)

To fixup this pull request, you need to add the backport labels for the needed
branches, such as:

  • backport-8./d is the label to automatically backport to the 8./d branch. /d is the digit

@mergify
Copy link
Contributor

mergify bot commented Sep 18, 2024

backport-8.x has been added to help with the transition to the new branch 8.x.
If you don't need it please use backport-skip label and remove the backport-8.x label.

@mergify mergify bot added the backport-8.x Automated backport to the 8.x branch with mergify label Sep 18, 2024
@mauri870 mauri870 force-pushed the benchmark-exec-http-request branch from 1ab0ed2 to b4ffcfe Compare September 18, 2024 13:29
@mauri870 mauri870 marked this pull request as ready for review September 18, 2024 13:37
@mauri870 mauri870 requested a review from a team as a code owner September 18, 2024 13:37
@elasticmachine
Copy link
Contributor

Pinging @elastic/elastic-agent-data-plane (Team:Elastic-Agent-Data-Plane)

This benchmark uses a hardcoded Hello World response. In a real world scenario
responses will range in size, specifically for _bulk responses. Updated the
benchmark to consider different sizes when benchmarking this function.
@mauri870 mauri870 force-pushed the benchmark-exec-http-request branch from b4ffcfe to b3fe46b Compare September 18, 2024 13:57
@pierrehilbert pierrehilbert requested review from belimawr and removed request for khushijain21 September 18, 2024 14:24
Copy link
Member

@rdner rdner left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks very good, thanks!

@mauri870 mauri870 merged commit ee157de into elastic:main Oct 1, 2024
mergify bot pushed a commit that referenced this pull request Oct 1, 2024
This benchmark uses a hardcoded Hello World response. In a real world scenario
responses will range in size, specifically for _bulk responses. Updated the
benchmark to consider different sizes when benchmarking this function.

(cherry picked from commit ee157de)
mauri870 added a commit that referenced this pull request Oct 1, 2024
#41062)

This benchmark uses a hardcoded Hello World response. In a real world scenario
responses will range in size, specifically for _bulk responses. Updated the
benchmark to consider different sizes when benchmarking this function.

(cherry picked from commit ee157de)

Co-authored-by: Mauri de Souza Meneguzzo <[email protected]>
@khushijain21 khushijain21 mentioned this pull request Jun 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport-8.x Automated backport to the 8.x branch with mergify cleanup Team:Elastic-Agent-Data-Plane Label for the Agent Data Plane team

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants