-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
AWS EC2 instance specs #925
Comments
Hi @TheSlackOne, we have some tips for running fullnode, maybe you can try these tips |
I recommend the i3en.2xlarge. |
Thanks for the recommendations, guys, I've also done the snapshot guide steps, and my node is still ~65 blocks away from last. It get to this height relatively fast (several thousands of blocks per hour) and then stucks on this difference. I don't have a clue now. Log shows:
|
Finally got synced with the I had to use the snapshots. At some points, it was 64 constantly, until suddenly was 1M blocks away. After restarting the node, got automatically synced. Took about ~4 days. |
I used two nvme disks mounted on i3en.2xlarge, which has better performance than aws ebs, in raid0. |
Aren't nvme physical disks? |
I'm not sure if it's a physical disk or not. However, it is much faster than ebs. |
I'm trying to get my full node synced with a
m5zn.3xlarge
, as the documentation describes, but it does not get synced, it oscillates 60-120 blocks from last. Not sure if its due to specs.The text was updated successfully, but these errors were encountered: