mirror/erigon-pulse
1
0
Fork 0
mirror of https://gitlab.com/pulsechaincom/erigon-pulse.git synced 2024-12-22 11:41:19 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Update README.md

Browse Source
This commit is contained in:
Igor Mandrigin 2020-08-02 17:56:56 +02:00 committed by GitHub
parent 7750a0b80f
commit 38ae733cdb
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 11 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
README.md
View File

@ -8,6 +8,9 @@
keep it stable and make no breaking changes but we don't guarantee anything. keep it stable and make no breaking changes but we don't guarantee anything.
Things can and will break.** Things can and will break.**
NB! <code>In-depth links are marked by the microscope sign (🔬) </code>
Turbo-Geth is a fork of [Go-Ethereum](https://github.com/ethereum/go-ethereum) with focus on performance. Turbo-Geth is a fork of [Go-Ethereum](https://github.com/ethereum/go-ethereum) with focus on performance.
The current version is currently based on Go-Ethereum 1.9.15. The current version is currently based on Go-Ethereum 1.9.15.
@ -24,13 +27,14 @@ Usage:
## Key features ## Key features
See more detailed [overview of functionality and current limitations](https://ledgerwatch.github.io/turbo_geth_release.html). <code>🔬 See more detailed [overview of functionality and current limitations](https://ledgerwatch.github.io/turbo_geth_release.html). It is being updated on recurring basis.</code>
It is being updated on recurring basis.
#### More Efficient State Storage #### More Efficient State Storage
**Flat KV storage.** Turbo-Geth uses a key-value database and storing accounts and storage in **Flat KV storage.** Turbo-Geth uses a key-value database and storing accounts and storage in
a simple way. **See our detailed DB walkthrough [here](./docs/programmers_guide/db_walkthrough.MD).** a simple way.
<code> 🔬 See our detailed DB walkthrough [here](./docs/programmers_guide/db_walkthrough.MD).</code>
**Preprocessing**. For some operations, turbo-geth uses temporary files to preprocess data before **Preprocessing**. For some operations, turbo-geth uses temporary files to preprocess data before
inserting it into the main DB. That reduces write amplification and inserting it into the main DB. That reduces write amplification and
@ -48,7 +52,7 @@ Turbo-Geth uses a rearchitected full sync algorithm from
[Go-Ethereum](https://github.com/ethereum/go-ethereum) that is split into [Go-Ethereum](https://github.com/ethereum/go-ethereum) that is split into
"stages". "stages".
See more detailed explanation in the [Staged Sync Readme](/eth/stagedsync/) <code>🔬 See more detailed explanation in the [Staged Sync Readme](/eth/stagedsync/)</code>
It uses the same network primitives and is compatible with regular go-ethereum It uses the same network primitives and is compatible with regular go-ethereum
nodes that are using full sync, you do not need any special sync capabilities nodes that are using full sync, you do not need any special sync capabilities
@ -75,7 +79,9 @@ Examples of stages are:
In turbo-geth RPC calls are extracted out of the main binary into a separate daemon. In turbo-geth RPC calls are extracted out of the main binary into a separate daemon.
This daemon can use both local or remote DBs. That means, that this RPC daemon This daemon can use both local or remote DBs. That means, that this RPC daemon
doesn't have to be running on the same machine as the main turbo-geth binary or doesn't have to be running on the same machine as the main turbo-geth binary or
it can run from a snapshot of a database for read-only calls. [Docs](./cmd/rpcdaemon/Readme.md) it can run from a snapshot of a database for read-only calls.
<code>🔬 See [RPC-Daemon docs](./cmd/rpcdaemon/Readme.md)</code>
**For local DB** **For local DB**