Skip to content
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

Poor performance for trace calls #4028

Closed
0x366 opened this issue Aug 2, 2023 · 3 comments
Closed

Poor performance for trace calls #4028

0x366 opened this issue Aug 2, 2023 · 3 comments
Labels
A-rpc Related to the RPC implementation C-enhancement New feature or request C-perf A change motivated by improving speed, memory usage or disk footprint S-stale This issue/PR is stale and will close with no further activity

Comments

@0x366
Copy link

0x366 commented Aug 2, 2023

Describe the feature

Im using debug_traceCall through IPC very extensively (executing a lot of simulations in parallel with arbitrary bytecode). I think it's around 100-1000 sims per block and up to 20-60 simultaneous requests. Previously I was running this same code on geth IPC and was getting decent times - like 200-400ms for 80 requests (it's 4 times * 20 simultaneous requests).

With reth my average time for these same requests are 400-800ms. Sometimes it becomes 2s+, while in geth I was getting everything under 1 second. I'm using --rpc-max-tracing-requests 1000.

Is there anything I can tweak?

Additional context

No response

@0x366 0x366 added C-enhancement New feature or request S-needs-triage This issue needs to be labelled labels Aug 2, 2023
@mattsse
Copy link
Collaborator

mattsse commented Aug 2, 2023

what kind of tracing requests?

nvm just saw the trace call

@0x366 could you please compare that with requests via websocket/http?

@mattsse mattsse added C-perf A change motivated by improving speed, memory usage or disk footprint A-rpc Related to the RPC implementation and removed S-needs-triage This issue needs to be labelled labels Aug 2, 2023
@github-actions
Copy link
Contributor

This issue is stale because it has been open for 14 days with no activity.

@github-actions github-actions bot added the S-stale This issue/PR is stale and will close with no further activity label Aug 17, 2023
@github-actions
Copy link
Contributor

This issue was closed because it has been inactive for 7 days since being marked as stale.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Aug 24, 2023
@github-project-automation github-project-automation bot moved this from Todo to Done in Reth Tracker Aug 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-rpc Related to the RPC implementation C-enhancement New feature or request C-perf A change motivated by improving speed, memory usage or disk footprint S-stale This issue/PR is stale and will close with no further activity
Projects
Archived in project
Development

No branches or pull requests

2 participants