1.9 KiB
TestNet debugging info
Currently we have two testnets, 'perf' and 'master', both on the master branch of the solana repo. Deploys happen at the top of every hour with the latest code. 'perf' has more cores for the client machine to flood the network with transactions until failure.
Deploy process
They are deployed with the ci/testnet-deploy.sh script. There is a scheduled buildkite job which runs to do the deploy,
look at testnet-deploy to see the agent which ran it and the logs. There is also a manual job to do the deploy manually..
Validators are selected based on their machine name and everyone gets the binaries installed from snap.
Where are the testnet logs?
For the client they are put in /tmp/solana; for validators and leaders they are in /var/snap/solana/current/.
You can also see the backtrace of the client by ssh'ing into the client node and doing:
$ sudo -u testnet-deploy
$ tmux attach -t solana
How do I reset the testnet?
Through buildkite.
How can I scale the tx generation rate?
Increase the TX rate by increasing the number of cores on the client machine which is running
bench-tps or run multiple clients. Decrease by lowering cores or using the rayon env
variable RAYON_NUM_THREADS=<xx>
How can I test a change on the testnet?
Currently, a merged PR is the only way to test a change on the testnet.
Adjusting the number of clients or validators on the testnet
- Go to the GCP Instance Group tab
- Find the client or validator instance group you'd like to adjust
- Edit it (pencil icon), change the "Number of instances", then click "Save" button
- Refresh until the change to number of instances has been executed
- Click the "New Build" button on the testnet-deploy buildkite job to initiate a redeploy of the network with the updated instance count.