You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To reduce memory pressure on Logstash we currently only allow to configure some events to be sent, this is a strict limit and doesn't reflect the dynamic nature of the events going through the stack.
Allowing users to set a maximum Batch Size in bytes would help reduce memory usage on the remote side. I think we could use this logic, cap to a specific amount of bytes each batch sent, if an element is higher than the maximum size it will be sent as a single request.
Also, I think this should be the default logic and we should drop the fixed batch size.
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
To reduce memory pressure on Logstash we currently only allow to configure some events to be sent, this is a strict limit and doesn't reflect the dynamic nature of the events going through the stack.
Allowing users to set a maximum Batch Size in bytes would help reduce memory usage on the remote side. I think we could use this logic, cap to a specific amount of bytes each batch sent, if an element is higher than the maximum size it will be sent as a single request.
Also, I think this should be the default logic and we should drop the fixed batch size.
The text was updated successfully, but these errors were encountered: