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
We have use cases where users are using ion-c's writers with sockets, in order to stream telemetry data over long periods of time. The current overhead and potential for memory fragmentation, when creating a new writer for each emitted record is too high for these cases.
We need to ensure that a writer can either already support long lifetimes, not relying on position or other values that could overflow, or implement functionality to allow writers to be reset without the overhead of freeing and re-allocating needed buffers.
The text was updated successfully, but these errors were encountered:
We have use cases where users are using ion-c's writers with sockets, in order to stream telemetry data over long periods of time. The current overhead and potential for memory fragmentation, when creating a new writer for each emitted record is too high for these cases.
We need to ensure that a writer can either already support long lifetimes, not relying on position or other values that could overflow, or implement functionality to allow writers to be reset without the overhead of freeing and re-allocating needed buffers.
The text was updated successfully, but these errors were encountered: