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
Do an initial poll of the ChannelManager write future immediately
In 7d856fe5b05d69b301fdb8a48352f3f3a16efca9 we moved to doing all
of our persistence operations in the (async) background processor
in parallel. This is great for slow persistence operations (eg with
remote persistence). However, the `ChannelManager` persistence is
very latency-sensitive (delays may lead to accidental
force-closures today) and thus we don't really want to wait on
network graph pruning or scorer time-stepping (which can be
somewhat slow).
Instead, we keep the new bulk-polling of the persistence operations
but immediately do a single step of the `ChannelManager`
persistence future after it is created. This should give it a
chance to get going - initializing whatever network sends or
connections need to happen - before we get busy doing CPU-intensive
stuff. While it may not actually make the persist happen in full,
it at least gives it a chance, and should make as much progress as
possible until a network resources is exhausted (eg send buffer is
full), at which point we need to wait on the network which is
almost certainly slow than the 1ms or so it will take to time-step
the scorer.
0 commit comments