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
{{ message }}
This repository has been archived by the owner on Feb 1, 2024. It is now read-only.
Currently there is no limit on how large telemetry client queue can grow. If used in some long running backend processes it can even cause memory overflow that could break the process.
I think we should look for a way to tell client to do auto flush when queue size is greater than 5mb (this value should be configurable).
To reduce resource consumption we can try to calculate each new entry size and then just increase the current size pointer in the client.
The text was updated successfully, but these errors were encountered:
Currently there is no limit on how large telemetry client queue can grow. If used in some long running backend processes it can even cause memory overflow that could break the process.
I think we should look for a way to tell client to do auto flush when queue size is greater than 5mb (this value should be configurable).
To reduce resource consumption we can try to calculate each new entry size and then just increase the current size pointer in the client.
The text was updated successfully, but these errors were encountered: