-
Notifications
You must be signed in to change notification settings - Fork 111
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deploy more Zebra or zcashd instances on testnet #1222
Comments
Maybe this work will scale out / let us deploy zebra nodes on testnet too |
In the most recent team sync, we decided to deploy a few nodes to mainnet and testnet for testing purposes. We can do this as soon as the hang PR in #1707 is merged. |
From the discord: quick thoughts
|
Yeah, we might want to keep the following deployments separate:
That way, it's easier for everyone to see what we have deployed, and to shut down things that aren't working. |
Motivation
The Zebra sync tests currently run on mainnet and testnet. Sometimes the testnet nodes are slow or unreliable, so the sync tests are unreliable.
Solution
Deploy about 10 Zebra or
zcashd
instances on testnet, to increase the average speed and reduce the average latency of testnet.Open Questions
Right now, we just need a few more Zebra or
zcashd
instances to stabilise the test network. We can deal with distribution, mining, and network speed later.Should the
zcashd
instances be configured to mine blocks?Where should they be located? How fast should they be?
Related Issues
Testnet sync fixes: Issue #1207 PR #1223
Tracking issue #745
The text was updated successfully, but these errors were encountered: