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
In our SPA we use @polkadot/rpc-provider^9.4.2 to connect 3 ScProviders
During the connection UI works fine, but just before sync finished message in console we face a 1.2 second freeze.
This happens every time when sync finished for 3 chains that we connect with ScProvider - Polkadot, Kusama, Westend.
We're not sending any requests to ScProvider, it just works by itself.
I recorded performance check in Chrome and saw a long wasm function execution
This is most likely the time it takes to verify the finality proofs.
While there's a "CPU limiter" in place, I suspect that it doesn't work because the inner FuturesUnordered immediately re-polls futures that are woken up during their execution.
In our SPA we use
@polkadot/rpc-provider^9.4.2
to connect 3ScProviders
During the connection UI works fine, but just before
sync finished
message in console we face a 1.2 second freeze.This happens every time when
sync finished
for 3 chains that we connect with ScProvider - Polkadot, Kusama, Westend.We're not sending any requests to ScProvider, it just works by itself.
I recorded performance check in Chrome and saw a long wasm function execution
Log message example: [sync-service-polkadot] GrandPa warp sync finished to #12229848 (0xea75…6e7b)
smoldot version 0.6.34
The text was updated successfully, but these errors were encountered: