-
Notifications
You must be signed in to change notification settings - Fork 134
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
content: Running multiple Beacon Nodes for Validators #340
Labels
Comments
The most efficient way to run a beacon validator combo is one validator client for each beacon node, and then add all the keys in that one validator client. Then just calibrate how many keys that 1:1 combo can handle. |
That makes sense. Is there a benchmark somewhere with data on # of
validators per Beacon Node?
I think it would be helpful for us to help Core Devs collect data and
metrics, given that Gnosis tokenomics will result in most node runners
running high validator counts per machine. The community has been
suggesting that there are limits to # of validator per node, which differs
from
It would be interesting to do a community-wide validator effort to collect
data on (a) hardware, and (b) perf metrics for given number of validators.
I'm spinning up my nodes over the holidays, and will start collecting some
data in Prometheus. Will probably need guidance in the new year on what the
existing best practices are.
## Previous studies:
https://www.symphonious.net/2022/04/06/exploring-eth2-cost-of-adding-validators/
https://ethereum.stackexchange.com/questions/132075/how-many-validators-can-run-with-single-consensus-client
- "no hard limit"
…On Fri, Dec 23, 2022 at 1:24 PM Lion - dapplion ***@***.***> wrote:
The most efficient way to run a beacon validator combo is one validator
client for each beacon node, and then add all the keys in that one
validator client. Then just calibrate how many keys that 1:1 combo can
handle.
—
Reply to this email directly, view it on GitHub
<#340 (comment)>,
or unsubscribe
<https:/notifications/unsubscribe-auth/AXOHUHNZLTPS5SEAMWXQ43TWOUZSFANCNFSM6AAAAAATHLMUM4>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
User
pyk
in Discord suggested running multiple beacon nodes could allow users to run high numbers of validators. This solves the issue where some validators miss their attestations.Todos
Resources
The text was updated successfully, but these errors were encountered: