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 use Tokio. However, most (all?) of the IO we are doing is blocking (see revault/revault_net#22).
I believe this is the cause for some pretty bad performances noticed of the coordinator under reasonable load. For instance, we would regularly encounter connection timeouts when testing on Signet and even more so when running revaultd's functional test suite. I believe fixing this issue would greatly reduce the runtime of the functional tests on revaultd.
So, here is what we need to do:
Confirm (or reject) the hypothesis that the performance loss / timeouts is due to a lack of real asynchronicity. The slowdowns can be reproduced using revaultd's functional test suite.
Once we have found the cause, obviously fix it here. If it's effectively due to blocking code we will probably need to fix Add a tokio feature revault_net#22.
The text was updated successfully, but these errors were encountered:
We use Tokio. However, most (all?) of the IO we are doing is blocking (see revault/revault_net#22).
I believe this is the cause for some pretty bad performances noticed of the coordinator under reasonable load. For instance, we would regularly encounter connection timeouts when testing on Signet and even more so when running
revaultd
's functional test suite. I believe fixing this issue would greatly reduce the runtime of the functional tests onrevaultd
.So, here is what we need to do:
revaultd
's functional test suite.tokio
feature revault_net#22.The text was updated successfully, but these errors were encountered: