-
Notifications
You must be signed in to change notification settings - Fork 190
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
tracers: refactor tracer api and avoid OOM while tracing #1581
Conversation
fccfb57
to
ab3222b
Compare
93cb466
to
397e334
Compare
"github.com/klaytn/klaytn/rlp" | ||
statedb2 "github.com/klaytn/klaytn/storage/statedb" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we need to change the name statedb2
here?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is changed from statedb
package to database
package here. So I think it is not necessary to use the name statedb2
here.
@jeongkyun-oh @aidan-kwon @kjhman21 Please take another look. It would be appreciate if you approve this PR. |
I'll merge this. If you have other opinion, feel free to leave a comment here. |
tracers: refactor tracer api and avoid OOM while tracing
Proposed changes
eth/tracers: move tracing APIs into eth/tracers ethereum/go-ethereum#22161
eth, les: fix tracer ethereum/go-ethereum#22473
eth: make traceChain avoid OOM on long-running tracing ethereum/go-ethereum#23736
Test result: test is done by tracing a block which contains 1000 txs(transferSignedTx, internalCallTx). CallTracer is used.
![image](https://user-images.githubusercontent.com/64360042/183639875-ab82b56b-3964-40f4-b822-46ccd960784e.png)
EN0(PR): It releases memory allocation immediately when tracing ends.
EN1(dev): It holds unnecessary memory allocation for a long time.
Types of changes
Please put an x in the boxes related to your change.
Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.
$ make test
)Related issues
Further comments
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...