# EPF5 Week11

This week focus on two things:

## 1. testing data usage for trace storage
So far I stored 3 traces with the following Geth command line arguments:

--vmtracer=filter 
--vmtrace.jsonconfig={"path": "/data/trace/filter", "config": {"callTracer": {}, "parityTracer": {}, "flatCallTracer": {"includePrecompiles": true, "convertParityErrors": true}}}

have stored the data with 45k blocks(from block 20563684 to 20609170), currently the data usage as below:

$ du -sh /data/trace/filter
19G     freeze
1.6G    trace

so the average data usage for a block is 0.46MB/tracer.

## 2. adjusting the trace filter PR

And the other one is split the large PR [#30255](https://github.com/ethereum/go-ethereum/pull/30255) into some smaller ones:

- [#30308](https://github.com/ethereum/go-ethereum/pull/30308)
- [#30337](https://github.com/ethereum/go-ethereum/pull/30337)

These new PRs are currently under review by @s1na, and there are still some adjustments needed.

## Next week plan

As previously showed, the average data usage for each trace is approximately 0.46MB. Therefore, the entire chain requires over 9TB of data for a single trace. To efficiently manage this, we need a method to prune the old traces. This requires introducing an additional command-line argument to specify the number of blocks to retain. By doing so, we can implement a circular storage technique to manage the data effectively.