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
Hi @splix , we're consistently seeing eth_getTransactionCount response times of above 500ms, while the same call to geth takes 50ms. We tried disabling the call for nodes outside the LB region but it didn't make a big difference.
Looks like NonceQuorum needs to confirm with at least 3 upstreams before responding, would it be possible to make this configurable or change it to something more sensible like NotLaggingQuorum(0) ? so it's consistent with eth_getBalance and eth_blockNumber.
The text was updated successfully, but these errors were encountered:
vdoflip
pushed a commit
to jit-strategies/dshackle
that referenced
this issue
Aug 1, 2023
Hi @splix , we're consistently seeing
eth_getTransactionCount
response times of above 500ms, while the same call to geth takes 50ms. We tried disabling the call for nodes outside the LB region but it didn't make a big difference.https://github.com/emeraldpay/dshackle/blob/master/src/main/kotlin/io/emeraldpay/dshackle/upstream/calls/DefaultEthereumMethods.kt#L97
Looks like
NonceQuorum
needs to confirm with at least 3 upstreams before responding, would it be possible to make this configurable or change it to something more sensible likeNotLaggingQuorum(0)
? so it's consistent witheth_getBalance
andeth_blockNumber
.The text was updated successfully, but these errors were encountered: