You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
it creating many databases on disk - and seems disk is the bottleneck (maybe ramfs can be used)
it seems ./tests - tests are mostly for stage_exec, but it using all components: Caplin, etc... maybe we should make them a bit lower-level (more like 'unit-tests' rather than 'integration')
The text was updated successfully, but these errors were encountered:
I spent some time investigating what is going. The main time consuming parts is read write to disk. I don't see anything specific what can be done to it but in fact it is pretty fast as I got average speed per test around 60ms and it just the amount of tests which is thousands. I tried to use ramps but it didn't make any positive results. What I've done is make tests to run in parallel which increased performance by 25% #12527
For integration tests I did more investigation and related to it make sense to have parallel execution only for BlockTest as other test doesn't shows any significant improvement or even get worse in performance:
github.com/erigontech/erigon/tests 407.674s
last bottleneck i know:
./tests
- tests are mostly forstage_exec
, but it using all components: Caplin, etc... maybe we should make them a bit lower-level (more like 'unit-tests' rather than 'integration')The text was updated successfully, but these errors were encountered: