Skip to content
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

Closed
TheSlackOne opened this issue May 23, 2022 · 7 comments
Closed

AWS EC2 instance specs #925

TheSlackOne opened this issue May 23, 2022 · 7 comments
Labels
question Further information is requested

Comments

@TheSlackOne
Copy link

TheSlackOne commented May 23, 2022

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.

@j75689 j75689 added the question Further information is requested label May 24, 2022
@j75689
Copy link
Contributor

j75689 commented May 24, 2022

Hi @TheSlackOne, we have some tips for running fullnode, maybe you can try these tips

#875
#502

@seonggwonyoon
Copy link

I recommend the i3en.2xlarge.

@TheSlackOne
Copy link
Author

TheSlackOne commented Jun 1, 2022

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:

t=2022-06-01T12:38:27+0000 lvl=info msg="Imported new state entries"             count=1152 elapsed=5.337ms     processed=184,858,934 pending=23606 trieretry=2   coderetry=0 duplicate=915 unexpected=2023
t=2022-06-01T12:38:28+0000 lvl=info msg="Imported new state entries"             count=1152 elapsed=5.671ms     processed=184,860,086 pending=22857 trieretry=2   coderetry=0 duplicate=915 unexpected=2023
t=2022-06-01T12:38:28+0000 lvl=info msg="Imported new state entries"             count=768  elapsed=3.645ms     processed=184,860,854 pending=23594 trieretry=2   coderetry=0 duplicate=915 unexpected=2023

@TheSlackOne
Copy link
Author

TheSlackOne commented Jun 9, 2022

Finally got synced with the m5zn.3xlarge instance, storage gp3 8000 iops and 250 troughtputs.

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.

@seonggwonyoon
Copy link

seonggwonyoon commented Jun 9, 2022

I used two nvme disks mounted on i3en.2xlarge, which has better performance than aws ebs, in raid0.
It took a day to complete the sync.
Also use the snapshots.

@TheSlackOne
Copy link
Author

TheSlackOne commented Jun 9, 2022

I used two nvme disks mounted on i3en.2xlarge, which has better performance than aws ebs, in raid0. It took a day to complete the sync. Also use the snapshots.

Aren't nvme physical disks?

@seonggwonyoon
Copy link

I used two nvme disks mounted on i3en.2xlarge, which has better performance than aws ebs, in raid0. It took a day to complete the sync. Also use the snapshots.

Aren't nvme physical disks?

I'm not sure if it's a physical disk or not.

However, it is much faster than ebs.

# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

3 participants