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 currently use libp2p's GossipSub to disseminate transactions for the txpool. Transactions can vary between 1kb ~ 200kb with 1kb being the most common one. GossipSub is a protocol that has to be tuned according to the "mode" of the message size.
Refer to the following doc for some more details on how to conduct simulations/research on decision about gossipsub params:
Simulations ran in live nodes spread across geographic locations to obtain data about message propagation time, size of message etc
tuning of gossipsub params and re-run simulation for the new values
overall reduction in bandwidth consumed by gossipsub, with lower latency for tx propagation
Why?
our executor is pretty fast, eventually the bottleneck for our tps will be consumption of transactions via gossipsub so it is useful to reduce this bottleneck.
The text was updated successfully, but these errors were encountered:
Description
We currently use libp2p's GossipSub to disseminate transactions for the txpool. Transactions can vary between 1kb ~ 200kb with 1kb being the most common one. GossipSub is a protocol that has to be tuned according to the "mode" of the message size.
Refer to the following doc for some more details on how to conduct simulations/research on decision about gossipsub params:
Definition of done
Why?
our executor is pretty fast, eventually the bottleneck for our tps will be consumption of transactions via gossipsub so it is useful to reduce this bottleneck.
The text was updated successfully, but these errors were encountered: