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
As a Block Node Engineer
I want to have a simple List<BlockItemUnparsed> as the object on the ring buffer
So that I have a consistent interface for all services that is entirely service-agnostic.
Technical Considerations:
We discussed object creation rate for all consumers and we determined it's not going to be an issue (around 3-5k/sec in normal usage and no more than 50k/sec under heavy load, which is very small as a percentage of the overall system).
We're now free to transmit block item batches as the type on the mediator ring buffer.
The text was updated successfully, but these errors were encountered:
We discussed object creation rate for all consumers and we determined it's not going to be an issue. We're now free to transmit block item batches as the type on the mediator ring buffer.
jsync-swirlds
changed the title
Feed List<BlockItemUnparsed> to a ring buffer for "historical" block streaming, if that's the requested process (task moved from #329)
Feed List<BlockItemUnparsed> to the ring buffer for streaming blocks
Feb 14, 2025
As a Block Node Engineer
I want to have a simple
List<BlockItemUnparsed>
as the object on the ring bufferSo that I have a consistent interface for all services that is entirely service-agnostic.
Technical Considerations:
We discussed object creation rate for all consumers and we determined it's not going to be an issue (around 3-5k/sec in normal usage and no more than 50k/sec under heavy load, which is very small as a percentage of the overall system).
We're now free to transmit block item batches as the type on the mediator ring buffer.
The text was updated successfully, but these errors were encountered: