Description

This PR introduces the functionality to run node with a separate trie database on a distinct disk or directory. This proposal aims to alleviate the bandwidth strain on the current key-value database, while also streamlining and simplifying the log-structured merge (LSM) of the database. These enhancements are anticipated to improve the read performance of the database and subsequently enhance the performance of geth.

Specifically, the PR includes the following features:

1. Support for running geth with a separate trie database. Users can set the --separatetrie flag to enable a separate database for storing trie data. Both hash-based and path-based trie databases are supported.
2. In the event of running with PBSS, the ancient state directory is also stored in the separate trie directory.
3. If users intend to utilize this feature for running a fullnode or validator, they must either run --separatetrie from genesis or make use of the provided snapshot containing the separate trie database.
4. The separate trie db use the subdirectory of /geth/chaindata which called "state". User can move the state subdirectory to any disk or directory and make a soft link called "state" under the /geth/chaindata

The inspected data below pertains to the execution of a fullnode in PBSS+Pebble mode across two separate disks.

This one shows the separate trie db

This one the db without trie data and ancient state

Rationale

Blow is the test result using different disk resource for trie.

avg import cost geth with single db is 324 ms while the cost of geth with seprated db is 291 ms.
The performance using seprated db has improve 10% (95 percent )

Example

// init geth with the separate trie db
./geth --datadir node  --state.scheme path --db.engine pebble --triedir trie init genesis.json

// run geth node with the separate  trie db
./geth --config config.toml --datadir node --triedir trie --cache 10000 --rpc.allow-unprotected-txs --syncmode full --state.scheme path

Changes

Notable changes:

• N/A