-
Notifications
You must be signed in to change notification settings - Fork 647
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bitfield-distribution
: use unbounded channels for own bitfields
#825
Comments
If bitfields are lagging, this will reduce parachain block production and will thus help reduce load on nodes - which is good! If we want bitfields to propagate faster we have to look into performance optimizations, bypassing natural back pressure will likely make matters worse. Prioritizing own bitfields might make sense, but I am still a bit uneasy about it. We need to make sure nodes are doing sensible stuff when close to overload. Bitfields in particular are a perfect point in the system to back-pressure, because almost no work will be wasted, things just get slower. This means if we find bitifields to be delayed because of load on the network bridge, then we should be looking into reducing that load. |
I think this is a short term solution, created for #824 mid-term |
This reverts commit 2fe5d29.
Change to the README.md instruction to run the node with the "release" folder instead of the "debug" folder.
* make finality verifier pallet instantiable * try to fix benchmarks * fix benchmarks compilation
* make finality verifier pallet instantiable * try to fix benchmarks * fix benchmarks compilation
* make finality verifier pallet instantiable * try to fix benchmarks * fix benchmarks compilation
* make finality verifier pallet instantiable * try to fix benchmarks * fix benchmarks compilation
* make finality verifier pallet instantiable * try to fix benchmarks * fix benchmarks compilation
* make finality verifier pallet instantiable * try to fix benchmarks * fix benchmarks compilation
* make finality verifier pallet instantiable * try to fix benchmarks * fix benchmarks compilation
* make finality verifier pallet instantiable * try to fix benchmarks * fix benchmarks compilation
* make finality verifier pallet instantiable * try to fix benchmarks * fix benchmarks compilation
* make finality verifier pallet instantiable * try to fix benchmarks * fix benchmarks compilation
* make finality verifier pallet instantiable * try to fix benchmarks * fix benchmarks compilation
* make finality verifier pallet instantiable * try to fix benchmarks * fix benchmarks compilation
* make finality verifier pallet instantiable * try to fix benchmarks * fix benchmarks compilation
Bitfield gossiping is handled here.
network-bridge
.This would make availability faster in situations when the
network-bridge
is clogged by too many messages:The text was updated successfully, but these errors were encountered: