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

specify number of real cores and threads per core #1306

Merged
merged 1 commit into from
Oct 19, 2023

Conversation

jdpinedac
Copy link
Contributor

What does this PR fix/introduce?

Taking into account that on AWS one must consider not only the instance's CPUs but also their equivalence to the vCPUs (virtual CPUs) offered by Amazon instances, the table specifies the equivalent for the recommended instance (t3.2xlarge).

Checklist

  • Docs are successfully building - yarn install && yarn run build.
  • All external links have been verified with yarn run check:externals.
  • My changes follow the Casper docs style guidelines.
  • All technical procedures have been tested (if you want help with this, mention it in Reviewers).

Reviewers

@bradjohnl @ipopescu

Copy link
Collaborator

@ipopescu ipopescu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

According to the EC2 user guide, this is correct. Thanks for the updates, @jdpinedac!

@ipopescu ipopescu merged commit eef9c95 into casper-network:feat-aws_nodes Oct 19, 2023
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants