fix: revert level update - #6834
Conversation
ae13083 to
a5dea46
Compare
|
At first glance looks like setting Not a lot of changes with |
|
Thanks @twoeths !! I was looking at metrics of fea1 and feat3 which both have about the same code (node 20 and all other 1.19 commits) and only feat1 shows that weird db pattern. feat3 and feat4 (the branch without the level update) look the same with a "normal" pattern of db activity. Not entirely convinced this is the root cause we are hunting for sadly....
|
Update: Last LevelDB update was quite a while ago... so you are def right @jeluard if level proves to be the issue we are hunting for https://github.com/google/leveldb/releases |
Performance Report鉁旓笍 no performance regression detected Full benchmark results
|
yes I wanted to only downgrade need to confirm the hypothesis through, testing in progress |
it was a docker deployment |





Motivation
classic-levelwas upgraded from 1.2.0 to 1.4.1 in #6795 and it caused a lot ofgcin docker deploymentThis PR is created on behalf of @matthewkeil
Description
lodestar/Dockerfile
Line 34 in 8b6ecc4
leveldownwithclassic-levelin db tests聽#6794 is optional for v1.19.0 so we can add it back with classic-level v1.20.0 later then create another issue for classic-level v1.4.1closes #6826
TODOs
The above hypothesis is not confirmed until the below step: