Specs
General Hardware
Multiple hardware configurations have been used in the Eluvio blockchain. The Upper End represents a configuration used by Eluvio currently, and it is over powered at present since the hardware is commingled with other applications in the runtime sandbox. The Upper End is presented for transparency, and the Lower End represents a more modest configuration that should suffice. This lower config may still be over powered given experience running validators in Google Cloud.
Lower End
| Type |
Details |
Qty |
Notes |
| CPU |
Intel/AMD CPU @ 3.1GHz |
16 “cores” |
An 8 core system presenting 16 thread/cores is sufficient (Hyper-threading). |
| Memory |
ECC Memory |
64GB |
More is better |
| Disk |
NVMe |
2TB |
e.g. Intel DC P4610 |
Upper End
| Type |
Details |
Qty |
Notes |
| CPU |
Intel/AMD CPU @ 2.5GHz |
8 “cores” |
A 4 core system presenting 8 thread/cores is sufficient (Hyper-threading) |
| Memory |
ECC Memory |
16GB |
More is better |
| Disk |
SSD/NVMe |
2TB |
Due to write activity, skimping on this should be avoided |
Cloud Guidance
Google Cloud
Eluvio has several validators running on Google Cloud. This is the current configuration used by the last large roll out.
| Type |
Details |
Qty |
Notes |
| Machine Type |
e2-highmem-2 |
1 |
Matches General Hardware Guide |
| Storage |
SSD persistent disk |
2TB |
Provisioned IOPs should not be needed |
AWS
No AWS nodes currently running elvmasterd as a validator. The following is a best guess using the hardware configuration in use at Google Cloud.
| Type |
Details |
Qty |
Notes |
| Machine Type |
r4.large |
1 |
Matches General Hardware Guide |
| Storage |
General SSD EBS |
2TB |
Provisioned IOPs should not be needed |