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
at the periods of high loads rollup-boost tends to open multiple (dozens) of TCP connections to the builder, which can deliver otherwise sequential updates from sequencer in arbitrary order.
there's only a 10ms difference between the fcu and getPayload request. I think by the time the fcu response was completed another getPayload request was received, initiating a new request. Is this not a bug caused by op-node having too little time between requests?
at the periods of high loads
rollup-boost
tends to open multiple (dozens) of TCP connections to the builder, which can deliver otherwise sequential updates from sequencer in arbitrary order.one example timeline (from
rollup-boost
logs):related logs from the builder side (timestamps are for when the response was sent back):
related to: #126
The text was updated successfully, but these errors were encountered: