-
Notifications
You must be signed in to change notification settings - Fork 57
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
besu node rpc returns data exception #39
Comments
Maybe |
How to disable Memory |
@rayn316 You can check the tracer config here: https://besu.hyperledger.org/public-networks/reference/api#debug_traceblockbynumber
|
There is still a problem in the return. After turning on disableMemory, it is still very large. After turning off all three projects, the data is all meaningless.
|
@rayn316 Could you please post what you are seeing with Geth? |
Issue with the size of the data returned by the debug_traceBlockByHash and debug_traceBlockByNumber methods in Besu compared to Geth, particularly when dealing with certain blocks. While Geth returns data in the range of kilobytes, Besu returns significantly larger data, sometimes exceeding 200MB. |
This issue is stale because it has been open for 6 months with no activity. |
os: ubuntu 22.04
network: mainnet
bin:
./besu-24.3.0/bin/besu --config-file=/node/full/linea/bin/config-mainnet.toml
There is a problem with besu software debug_traceBlockByHash debug_traceBlockByNumber. Compared with geth, the data returned is abnormally large at certain times.
besu returns 200MB+ data (Some blocks are even larger)
geth returns 92KB data
The text was updated successfully, but these errors were encountered: