[exporter/datadog] use the same default batch configs as exporterhelper #43848
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Set sending queue batch default values to match exporter helper default: flush timeout 200ms, min size 8192, no max size.
Context: when we applied the default batch values in #43419 to datadog-agent, we observed a regression in performance tests. Setting the batch values back to batch processor default values (also the exporter helper default) fixes the regression, thus this change.
A downside is if users ran into 413 payload too large errors, they now need to set the batch values in datadog::sending_queue::batch. This is reflected in the readme.
Link to tracking issue
related to #43082