forks/go-ethereum
1
0
Fork 1
mirror of https://github.com/ethereum/go-ethereum.git synced 2026-07-28 07:36:44 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 3
go-ethereum/node
History
rroblak ebc7dc231a
Add CLI flags to config LevelDB table/total sizes (#981) 
* Add CLI flags to config LevelDB table/total sizes

I wired up CLI flags to allow configuring LevelDB table and total sizes:
  - `--leveldb.compaction.table.size`, LevelDB SSTable file size factor in MiB (default: 2)
  - `--leveldb.compaction.table.multiplier`, multiplier on LevelDB SSTable file size (default: 1)
  - `--leveldb.compaction.total.size`, total size factor in MiB of LevelDB levels (default: 10)
  - `--leveldb.compaction.total.multiplier`, multiplier on LevelDB total level size (default: 10)

N.B. that the default values for these configs are exactly the same as
before this changset and so Bor behavior should not change unless these
flags are deliberately overridden. Bor/Geth inherited the default values
from [the `goleveldb`
defaults](126854af5e/leveldb/opt/options.go).

We (Alchemy) found it necessary to override these configs as follows to
keep Bor archive nodes tracking the canonical chain:
  - `--leveldb.compaction.table.size=4`
  - `--leveldb.compaction.total.size=20`

These overrides double the size of LevelDB SSTable files (2 MiB -> 4
MiB) and also the total amount of data in each level (100 MiB -> 200
MiB, 1,000 MiB -> 2,000 MiB, etc.). The idea is to have LevelDB read and
write data in larger chunks while keeping the proportional frequency of
compaction operations the same as in the original defaults defined by
Dean and Ghemawat.

Without these overrides we found that our archive nodes would tend to
fall into a "LevelDB compaction loop of death" where the incoming stream
of blockchain data could not be flowed into LevelDB's structure quickly
enough, resulting in the node blocking writes for long periods of time
while LevelDB's single-threaded compaction organized the data.  Over
time the nodes would fall farther and farther behind the canonical chain
head, metaphorically dying a slow node's death.

These configs can be changed on existing node databases (resyncing is
not necessary). LevelDB appears to work correctly with SSTable files of
different sizes. Note that the database does not undergo any sort of
migration when changing these configs. Only newly-written files (due to
new data or compaction) are affected by these configs.

* Update docs

* Adjust line spacing for linter

* Replace map with `ExtraDBConfig`

* Rename `LevelDbConfig` to `ExtraDBConfig`

* Regenerate docs
2023-09-12 12:09:26 +02:00
..
api.go dev: fix: most of wsl lint issues 2023-06-15 15:48:26 +02:00
api_test.go dev: fix: most of wsl lint issues 2023-06-15 15:48:26 +02:00
config.go dev: fix: all remaining lint issues 2023-06-19 11:39:59 +02:00
config_test.go dev: fix: most of wsl lint issues 2023-06-15 15:48:26 +02:00
defaults.go dev: fix: most of wsl lint issues 2023-06-15 15:48:26 +02:00
doc.go build: upgrade to go 1.19 (#25726) 2022-09-10 13:25:40 +02:00
endpoints.go dev: fix: most of wsl lint issues 2023-06-15 15:48:26 +02:00
errors.go dev: fix: most of wsl lint issues 2023-06-15 15:48:26 +02:00
jwt_auth.go dev: fix: most of wsl lint issues 2023-06-15 15:48:26 +02:00
jwt_handler.go dev: fix: most of wsl lint issues 2023-06-15 15:48:26 +02:00
lifecycle.go node: refactor package node (#21105) 2020-08-03 19:40:46 +02:00
node.go Add CLI flags to config LevelDB table/total sizes (#981) 2023-09-12 12:09:26 +02:00
node_auth_test.go dev: fix: tests failing due to t.Parallel 2023-06-21 15:03:16 +02:00
node_example_test.go dev: fix: most of wsl lint issues 2023-06-15 15:48:26 +02:00
node_test.go Add CLI flags to config LevelDB table/total sizes (#981) 2023-09-12 12:09:26 +02:00
rpcstack.go Merge branch 'develop' into mardizzone/upstream-merge 2023-07-24 14:19:30 +05:30
rpcstack_test.go dev: fix: all remaining lint issues 2023-06-19 11:39:59 +02:00
utils_test.go dev: fix: most of wsl lint issues 2023-06-15 15:48:26 +02:00