0a48344dfe
This adds a few tiny fixes for les and the p2p simulation framework: LES Parts - Keep the LES-SERVER connection even it's non-synced We had this idea to reject the connections in LES protocol if the les-server itself is not synced. However, in LES protocol we will also receive the connection from another les-server. In this case even the local node is not synced yet, we should keep the tcp connection for other protocols(e.g. eth protocol). - Don't count "invalid message" for non-existing GetBlockHeadersMsg request In the eth syncing mechanism (full sync, fast sync, light sync), it will try to fetch some non-existent blocks or headers(to ensure we indeed download all the missing chain). In this case, it's possible that the les-server will receive the request for non-existent headers. So don't count it as the "invalid message" for scheduling dropping. - Copy the announce object in the closure Before the les-server pushes the latest headers to all connected clients, it will create a closure and queue it in the underlying request scheduler. In some scenarios it's problematic. E.g, in private networks, the block can be mined very fast. So before the first closure is executed, we may already update the latest_announce object. So actually the "announce" object we want to send is replaced. The downsize is the client will receive two announces with the same td and then drop the server. P2P Simulation Framework - Don't double register the protocol services in p2p-simulation "Start". The protocols upon the devp2p are registered in the "New node stage". So don't reigster them again when starting a node in the p2p simulation framework - Add one more new config field "ExternalSigner", in order to use clef service in the framework. # Conflicts: # les/server_handler.go |
||
|---|---|---|
| .buildkite | ||
| .circleci | ||
| .github | ||
| .golangci | ||
| accounts | ||
| cmd | ||
| common | ||
| consensus | ||
| console/prompt | ||
| contracts/checkpointoracle | ||
| core | ||
| crypto | ||
| debug-web-ui | ||
| design | ||
| docs | ||
| eth | ||
| ethclient | ||
| ethdb | ||
| ethstats | ||
| event | ||
| graphql | ||
| interfaces | ||
| internal | ||
| log | ||
| metrics | ||
| migrations | ||
| miner | ||
| node | ||
| p2p | ||
| params | ||
| rlp | ||
| rpc | ||
| signer | ||
| tests | ||
| turbo | ||
| visual | ||
| .dockerignore | ||
| .gitattributes | ||
| .gitignore | ||
| .gitmodules | ||
| .golangci.yml | ||
| .mailmap | ||
| .readthedocs.yml | ||
| .travis.yml | ||
| appveyor.yml | ||
| AUTHORS | ||
| circle.yml | ||
| COPYING | ||
| COPYING.LESSER | ||
| docker-compose.yml | ||
| Dockerfile | ||
| fuzzbuzz.yaml | ||
| go.mod | ||
| go.sum | ||
| interfaces.go | ||
| Makefile | ||
| nightly.sh | ||
| README.geth.md | ||
| README.md | ||
| RELEASE_INSTRUCTIONS.md | ||
| SECURITY.md | ||
| to-merge.txt | ||
| UPGRADE_INFO.md | ||
Turbo-Geth
Turbo-Geth is a fork of Go-Ethereum with focus on performance. 
Table of contents
NB! In-depth links are marked by the microscope sign (🔬)
Disclaimer: this software is currenly a tech preview. We will do our best to keep it stable and make no breaking changes but we don't guarantee anything. Things can and will break.
The current version is currently based on Go-Ethereum 1.9.15.
System Requirements
About 830 GB of free disk storage (630 GB state storage, 200GB temp files)
16 or 32 GB of RAM is recommended
🔬 more info on disk storage is here here)
Usage
> git clone --recurse-submodules -j8 https://github.com/ledgerwatch/turbo-geth.git && cd turbo-geth
> make tg
> ./build/bin/tg
Key features
🔬 See more detailed overview of functionality and current limitations. It is being updated on recurring basis.
More Efficient State Storage
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.
Preprocessing. For some operations, turbo-geth uses temporary files to preprocess data before inserting it into the main DB. That reduces write amplification and DB inserts sometimes are orders of magnitude quicker.
🔬 See our detailed ETL explanation here.
Plain state.
Single accounts/state trie. Turbo-Geth uses a single Merkle trie for both accounts and the storage.
Faster Initial Sync
Turbo-Geth uses a rearchitected full sync algorithm from Go-Ethereum that is split into "stages".
🔬 See more detailed explanation in the Staged Sync Readme
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 for turbo-geth to sync.
When reimagining the full sync, we focused on batching data together and minimize DB overwrites. That makes it possible to sync Ethereum mainnet in under 2 days if you have a fast enough network connection and an SSD drive.
Examples of stages are:
-
Downloading headers;
-
Downloading block bodies;
-
Executing blocks;
-
Validating root hashes and building intermediate hashes for the state Merkle trie;
-
And more...
JSON-RPC 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 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.
🔬 See RPC-Daemon docs
For local DB
> make rpcdaemon
> ./build/bin/rpcdaemon --chaindata ~/Library/TurboGeth/tg/chaindata --http.api=eth,debug,net
For remote DB
Run turbo-geth in one terminal window
> ./build/bin/tg --private.api.addr=localhost:9090
Run RPC daemon
> ./build/bin/rpcdaemon --private.api.addr=localhost:9090
Supported JSON-RPC calls (eth, debug, net, web3):
For a details on the implementation status of each command, see this table.
Grafana dashboard:
docker-compose up prometheus grafana, detailed docs.
Or run all components by docker-compose
Next command starts: turbo-geth on port 30303, rpcdaemon 8545, prometheus 9090, grafana 3000
docker-compose build
XDG_DATA_HOME=/preferred/data/folder docker-compose up
Getting in touch
Turbo-Geth Discord Server
The main discussions are happening on our Discord server.
To get an invite, send an email to tg [at] torquem.ch with your name, occupation,
a brief explanation of why you want to join the Discord, and how you heard about Turbo-Geth.
Reporting security issues/concerns
Send an email to security [at] torquem.ch.
Team
Core contributors:
-
Alexey Akhunov (@realLedgerwatch)
-
Alex Sharov (AskAlexSharov)
-
Andrew Ashikhmin (yperbasis)
-
Boris Petrov (b00ris)
-
Eugene Danilenko (JekaMas)
-
Igor Mandrigin (@mandrigin)
-
Giulio Rebuffo
-
Thomas Jay Rush (@tjayrush)
Thanks to:
-
All contributors of Turbo-Geth
-
All contributors of Go-Ethereum
-
Our special respect and graditude is to the core team of Go-Ethereum. Keep up the great job!
Happy testing! 🥤
Known issues
1. htop shows incorrect memory usage
TurboGeth's internal DB (LMDB) using MemoryMap - when OS does manage all read, write, cache operations instead of Application
(linux, windows)
htop on column res shows memory of "App + OS used to hold page cache for given App",
but it's not informative, because if htop says that app using 90% of memory you still
can run 3 more instances of app on the same machine - because most of that 90% is "OS pages cache".
OS automatically free this cache any time it needs memory.
Smaller "page cache size" may not impact performance of TurboGeth at all.
Next tools show correct memory usage of TurboGeth:
vmmap -summary PID | grep -i "Physical footprint". Withoutgrepyou can see details -section MALLOC ZONE column Resident Sizeshows App memory usage,section REGION TYPE column Resident Sizeshows OS pages cache size.Prometheusdashboard shows memory of Go app without OS pages cache (make prometheus, open in browserlocalhost:3000, credentialsadmin/admin)cat /proc/<PID>/smaps
TurboGeth uses ~4Gb of RAM during genesis sync and < 1Gb during normal work. OS pages cache can utilize unlimited amount of memory.
Warning: Multiple instances of TG on same machine will touch Disk concurrently, it impacts performance - one of main TG optimisations: "reduce Disk random access". "Blocks Execution stage" still does much random reads - this is reason why it's slowest stage. We do not recommend run multiple genesis syncs on same Disk. If genesis sync passed, then it's fine to run multiple TG on same Disk.