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

Create a list of hardware we support #3075

Closed
chefsale opened this issue Aug 4, 2020 · 6 comments
Closed

Create a list of hardware we support #3075

chefsale opened this issue Aug 4, 2020 · 6 comments
Assignees
Labels
T-SRE Team: issues relevant to the SRE team

Comments

@chefsale
Copy link
Contributor

chefsale commented Aug 4, 2020

No description provided.

@chefsale chefsale added the T-SRE Team: issues relevant to the SRE team label Aug 4, 2020
@bowenwang1996 bowenwang1996 changed the title Create a list of hardware we support (specific to wasmer) Create a list of hardware we support Aug 6, 2020
@bowenwang1996
Copy link
Collaborator

So far we have

  • CPU must support AVX instructions
  • Disk must be SSD

We can add such checks to nearup as well.

@olonho
Copy link
Contributor

olonho commented Aug 18, 2020

Actually SSD requirement is an optional one, it shall not affect correctness, only performance. AVX now is checked automatically, and we are planning to eventually eliminate it as a hard requirement using updated Wasm VM. Practically speaking our machine requirements include:

  • x86-64 machine (with AVX support currently)
  • Linux operating system. @bowenwang1996 which version of Linux do we use for building node software? glibc is only backward compatible, so this is likely a limiting factor.
  • Do we want to support running nodes on Windows/macOS?
  • Do we have RAM requirements? At least 8G of RAM seems natural.

@bowenwang1996
Copy link
Collaborator

while SSD doesn't affect correctness, if a node does not use SSD it cannot keep up with the network and therefore I consider it to be required.

@olonho
Copy link
Contributor

olonho commented Aug 25, 2020

Think if it can keep up with the network depends on multiple factors, and currently AFAIK we don't have enough data to confirm or deny this hypothesis.

@bowenwang1996
Copy link
Collaborator

I did investigate this in the past. When we use HDD garbage collection became very slow because of storage read. Some read can take more than 100ms.

@chefsale
Copy link
Contributor Author

chefsale commented Sep 8, 2020

Can we close this issue? cc: @bowenwang1996

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
T-SRE Team: issues relevant to the SRE team
Projects
None yet
Development

No branches or pull requests

3 participants