| CHAIN_ID="juno-1" | |
| MODE="signer1" | |
| NODE_HOME_DIR=$HOME/.juno | |
| # horcrux version | |
| VERSION="v2.0.0-rc3" | |
| SIGNER_ONE="10.0.0.2" | |
| SIGNER_TWO="10.0.0.3" | |
| SIGNER_THREE="10.0.0.4" |
State sync can greatly speed up the time it takes to bring a node online, and the smaller state size will make processing the epoch much faster. There is however a bug that affects osmosisd v5.0.0-v6.0.1 which causes the replay to fail after syncing
This walks through the steps to bring up a new node using state sync on osmosis v6.0.1, this will likely be outdated pretty quickly (Jan 2, 2022) once the bug is fixed.
| #!/bin/bash | |
| ROCKSDB_VERSION=5.11.3 | |
| #Run as a root user | |
| if [ "$EUID" -ne 0 ] | |
| then echo "Please run as root (with sudo command)" | |
| exit | |
| fi |
$ uname -r
For this configuration you can use web server you like, i decided, because i work mostly with it to use nginx.
Generally, properly configured nginx can handle up to 400K to 500K requests per second (clustered), most what i saw is 50K to 80K (non-clustered) requests per second and 30% CPU load, course, this was 2 x Intel Xeon with HyperThreading enabled, but it can work without problem on slower machines.
You must understand that this config is used in testing environment and not in production so you will need to find a way to implement most of those features best possible for your servers.