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 can refactor the wiring of the Reactor code to be able to process multiple messages at the same time. This is likely crucial for stopping long message processing times from blocking other messages from coming in.
While this isn't a bottleneck atm, as the big blonks testnet was not using this and was capable of hitting 27MB/s even without such changes. However it would likely dramatically limit the damage that could be done by inscription events, where the network was being spammed with many small stateful messages that each requires blocking calls to CheckTx.
this would get us to the point where multiple reactors could process messages at the same time. In the future, it might be more advantageous to refactor further, for example to enable each channel to process messages independently.
The text was updated successfully, but these errors were encountered:
We can refactor the wiring of the
Reactor
code to be able to process multiple messages at the same time. This is likely crucial for stopping long message processing times from blocking other messages from coming in.While this isn't a bottleneck atm, as the big blonks testnet was not using this and was capable of hitting 27MB/s even without such changes. However it would likely dramatically limit the damage that could be done by inscription events, where the network was being spammed with many small stateful messages that each requires blocking calls to
CheckTx
.relevant code and potential implementations below
celestia-core/p2p/conn/connection.go
Lines 558 to 666 in 8581b47
celestia-core/p2p/peer.go
Lines 548 to 586 in 8581b47
potential implementation https://github.com/cometbft/cometbft/pull/3230/files
this would get us to the point where multiple reactors could process messages at the same time. In the future, it might be more advantageous to refactor further, for example to enable each channel to process messages independently.
The text was updated successfully, but these errors were encountered: