-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
perf(opentelemetry): increase queue max batch size #12488
Conversation
The max batch size for Opentelemetry was set to the default value: 1 the value actually refers to the number of spans in a batch, so we are increasing the default value to 200 which corresponds to what the default value used to be with the "old" queue implementation.
0df0e06
to
5d3c48e
Compare
Backport failed for Please cherry-pick the changes locally and resolve any conflicts. git fetch origin release/3.3.x
git worktree add -d .worktree/backport-12488-to-release/3.3.x origin/release/3.3.x
cd .worktree/backport-12488-to-release/3.3.x
git switch --create backport-12488-to-release/3.3.x
git cherry-pick -x c7cb900f4919e6b320b7bdf9132cfa4747679760 |
The max batch size for Opentelemetry was set to the default value: 1 the value actually refers to the number of spans in a batch, so we are increasing the default value to 200 which corresponds to what the default value used to be with the "old" queue implementation. (cherry picked from commit c7cb900)
Successfully created backport PR for |
The max batch size for Opentelemetry was set to the default value: 1 the value actually refers to the number of spans in a batch, so we are increasing the default value to 200 which corresponds to what the default value used to be with the "old" queue implementation. (cherry picked from commit c7cb900)
Successfully created backport PR for |
The max batch size for Opentelemetry was set to the default value: 1 the value actually refers to the number of spans in a batch, so we are increasing the default value to 200 which corresponds to what the default value used to be with the "old" queue implementation. (cherry picked from commit c7cb900)
The max batch size for Opentelemetry was set to the default value: 1 the value actually refers to the number of spans in a batch, so we are increasing the default value to 200 which corresponds to what the default value used to be with the "old" queue implementation. (cherry picked from commit c7cb900)
The max batch size for Opentelemetry was set to the default value: 1 the value actually refers to the number of spans in a batch, so we are increasing the default value to 200 which corresponds to what the default value used to be with the "old" queue implementation.
The max batch size for Opentelemetry was set to the default value: 1 the value actually refers to the number of spans in a batch, so we are increasing the default value to 200 which corresponds to what the default value used to be with the "old" queue implementation.
Backport failed for Please cherry-pick the changes locally and resolve any conflicts. git fetch origin release/3.3.x
git worktree add -d .worktree/backport-12488-to-release/3.3.x origin/release/3.3.x
cd .worktree/backport-12488-to-release/3.3.x
git switch --create backport-12488-to-release/3.3.x
git cherry-pick -x c7cb900f4919e6b320b7bdf9132cfa4747679760 |
Backport failed for Please cherry-pick the changes locally and resolve any conflicts. git fetch origin release/3.4.x
git worktree add -d .worktree/backport-12488-to-release/3.4.x origin/release/3.4.x
cd .worktree/backport-12488-to-release/3.4.x
git switch --create backport-12488-to-release/3.4.x
git cherry-pick -x c7cb900f4919e6b320b7bdf9132cfa4747679760 |
Backport failed for Please cherry-pick the changes locally and resolve any conflicts. git fetch origin release/3.5.x
git worktree add -d .worktree/backport-12488-to-release/3.5.x origin/release/3.5.x
cd .worktree/backport-12488-to-release/3.5.x
git switch --create backport-12488-to-release/3.5.x
git cherry-pick -x c7cb900f4919e6b320b7bdf9132cfa4747679760 |
The max batch size for Opentelemetry was set to the default value: 1 the value actually refers to the number of spans in a batch, so we are increasing the default value to 200 which corresponds to what the default value used to be with the "old" queue implementation. (cherry picked from commit c7cb900)
Successfully created cherry-pick PR for |
Successfully created backport PR for |
The max batch size for Opentelemetry was set to the default value: 1 the value actually refers to the number of spans in a batch, so we are increasing the default value to 200 which corresponds to what the default value used to be with the "old" queue implementation. (cherry picked from commit c7cb900)
Summary
The max batch size for Opentelemetry was set to the default value: 1 the value actually refers to the number of spans in a batch, so we are increasing the default value to 200 which corresponds to what the default value used to be with the "old" queue implementation.
Checklist
changelog/unreleased/kong
orskip-changelog
label added on PR if changelog is unnecessary. README.mdIssue reference
https://konghq.atlassian.net/browse/KAG-3173