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
I need to write MCAP files in a time critical data streaming system. I have a buffer for the streaming data, and when some event triggers, I need to offload the buffered data to MCAP files, in some other cases, I need to write the stream data to the MCAP file directly.
I know MCAP library buffers data in memory first, do compression and then flush to disk when the buffer size reached. I am wondering in my case, would disk write be a botternect given that the MCAP library is already buffered? Would it be helpful/make sense if I use a dedicated thread for the MCAP writer?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello,
I need to write MCAP files in a time critical data streaming system. I have a buffer for the streaming data, and when some event triggers, I need to offload the buffered data to MCAP files, in some other cases, I need to write the stream data to the MCAP file directly.
I know MCAP library buffers data in memory first, do compression and then flush to disk when the buffer size reached. I am wondering in my case, would disk write be a botternect given that the MCAP library is already buffered? Would it be helpful/make sense if I use a dedicated thread for the MCAP writer?
Beta Was this translation helpful? Give feedback.
All reactions