Open cielu opened 3 months ago
The first request is for historical data from a long time ago, and the second request is for the most recent signature.
@cielu Is there any associated spike in CPU usage noticed? I am looking at a similar problem
@avinashbo There should be some impact, but I'm not sure. My CPU is EPYC 7502, which is only 2.5GHz. I think this is a problem. We are preparing to replace this server, but we don't know what configuration is more suitable. We have already changed and configured multiple servers, and I feel that the read and write speed of Nvme can't keep up.
@avinashbo But I think there must be something wrong with this v1.18.15 version, because I don't have these problems when I use v1.17.34, but the synchronization speed is not that fast
Problem
I upgraded my rpc node to v1.18.15 today, and the synchronization has been completed. However, when I request: getTransaction, the response is very slow and it takes 5sec ~ 20 seconds to wait.
This problem seems to occur only in non-full nodes, and the signature requested was a long time ago. It should return null, but it has been responding.
Proposed Solution
response null:
{"jsonrpc":"2.0","result": null,"id":1}