-
Notifications
You must be signed in to change notification settings - Fork 676
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
RPC node falls behind since >=v11 when queried #2733
Comments
Possibly related to #2415, #2726. Have you tried running your node in debug mode (temporarily) and checking which RPC endpoints are being queried?
Please note that you may need to set up additional software in case you are exposing your node to the public, such as a load balancer or a proxy, much like you would if you were exposing any other backend service. |
The following gRPC requests are used:
In particular |
By the way, I read through some of the suggestions in #2415, but this is a perf. regression. We have solved in creative ways, but the nodes consistently die. edit: We trust Interchain's/this repo's interpretation of the blockchain state, adding a layer of indrection like an explorer, while possible, is something we would very much like to avoid. |
Indeed @exp0nge , every layer and redirection adds overhead and complexity - thats something that we always want to avoid if possible. The performance bottlenecks that you've mentioned, regression or otherwise, lie with the lower levels of the stack (SDK / Comet). If theres a specific endpoint that has regressed in terms of performance, then we can check with the relevant teams. Are the following endpoints |
Unsure exactly which call causes this as we use the ones above listed, but the most heavily used ones are: |
@exp0nge Hey, has this issue been fixed on |
@exp0nge Is this issue stil relevant for you on |
I think we can close this, I don't see these issues anymore. We also maintain a large enough pool of nodes that this is no longer an issue for us. |
Summary of Bug
We have noticed severe performance degradation since v11 where nodes we query against fall behind very quickly. Attached below are some logs. This behavior is not notice-able in non-RPC mode nodes (nodes that are not being queried).
cc @ckarabats
Version
>=v11
Steps to Reproduce
For Admin Use
The text was updated successfully, but these errors were encountered: