We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
We use some heuristic to adjust the max buffer size, max decoder size and max requests.
apm-server/internal/beater/beater.go
Lines 543 to 552 in 6309df6
Lines 769 to 799 in 6309df6
This formulas are really old and we had a lot of improvements since then, we should revisit them to ensure we are not underutilizing apm-server
The text was updated successfully, but these errors were encountered:
We could easily update the max_requests formula to memLimit * 2 instead of memLimit * 1.5.
max_requests
memLimit * 2
memLimit * 1.5
// 1 2 4 8 15 30 // 12 14 18 26 40 70 maxRequests := int(float64(10) + memLimit*2) if maxRequests > 80 { maxRequests = 80 }
Sorry, something went wrong.
I've updated the benchmark report in https://github.com/elastic/apm-dev/pull/1088.
Please review and do not hesitate to ask questions.
@simitt @kruskall @marclop @1pkg
rubvs
No branches or pull requests
We use some heuristic to adjust the max buffer size, max decoder size and max requests.
apm-server/internal/beater/beater.go
Lines 543 to 552 in 6309df6
apm-server/internal/beater/beater.go
Lines 769 to 799 in 6309df6
This formulas are really old and we had a lot of improvements since then, we should revisit them to ensure we are not underutilizing apm-server
The text was updated successfully, but these errors were encountered: