The HC Net is a live system and the hardware requirements will grow along with usage of the network. Please keep this in mind as you decide what hardware you want to use for your HC Net integration.
If you opt to go with the minimum requirements that we have listed below, you may experience some lag during times of peak traffic on the network as your node tries to catch up to the rest of the network. For a smooth experience you should opt to go with the recommended hardware requirements listed for each service.
We will do our best to keep this doc up-to-date as we make further improvements to the codebase.
Instances of HCNet-Core are part of the network as a node and therefore need to be large enough to support the volume on the network.
CPU: 4-Core (8-Thread) Intel i7/Xeon or equivalent (c5.xlarge on AWS)
RAM: 8GB DDR4
SSD: 64GB
CPU: 8-Core (16-Thread) Intel i7/Xeon or equivalent (c5.2xlarge on AWS)
RAM: 16GB DDR4
SSD: 120GB
Instances of Aurora ingest data from the network and therefore need to be large enough to support ingesting all of the latest transactions on the network.
There is a significant amount of computation that is done on the DB side of Aurora, these requirements are only for the application side of aurora. If you are going by these requirements then you will need to account for using a larger machine if using the same machine for the DB, or a separate machine for the DB altogether.
CPU: 8-Core (16-Thread) Intel i7/Xeon or equivalent (c5.2xlarge on AWS)
RAM: 16GB DDR4
SSD: 64GB
CPU: 16-Core (32-Thread) Intel i7/Xeon or equivalent (c5.4xlarge on AWS)
RAM: 32GB DDR4
SSD: 120GB
The hardware requirements for these Institutional Host services depend on your own internal usage, i.e. these hardware requirements will not increase as the volume on the network increases. Our suggestions below assume that you will run one machine for each service, although you can combine services onto a single machine with a larger capacity using VMs if you prefer.
CPU: 2-Core (4-Thread) Intel i7/Xeon or equivalent (c5.large on AWS)
RAM: 4GB DDR3/DDR4
SSD: Needs a DB to hold processed transactions. Above CPU and RAM requirements don’t account for running this database’s hardware. DB size depends on your usage of the network. 20GB seems like a good starting point.
CPU: 4-Core (8-Thread) Intel i7/Xeon or equivalent (c5.xlarge on AWS)
RAM: 8GB DDR4
SSD: Needs a DB to hold processed transactions. Above CPU and RAM requirements don’t account for running this database’s hardware. DB size depends on your usage of the network. 20GB seems like a good starting point.
CPU: 2-Core (4-Thread) Intel i7/Xeon or equivalent (c5.large on AWS)
RAM: 4GB DDR3/DDR4
SSD: Needs a DB to hold mapping table. Above CPU and RAM requirements don’t account for running this database’s hardware. DB size depends on how many accounts you have. See callbacks for more information.
CPU: 4-Core (8-Thread) Intel i7/Xeon or equivalent (c5.xlarge on AWS)
RAM: 8GB DDR4
SSD: Needs a DB to hold mapping table. Above CPU and RAM requirements don’t account for running this database’s hardware. DB size depends on how many accounts you have. See callbacks for more information.
CPU: 2-Core (4-Thread) Intel i7/Xeon or equivalent (c5.large on AWS)
RAM: 4GB DDR3/DDR4
SSD:Needs a DB to hold processed transactions. Above CPU and RAM requirements don’t account for running this database’s hardware. DB size depends on your usage of the network. 20GB seems like a good starting point.
CPU: 4-Core (8-Thread) Intel i7/Xeon or equivalent (c5.xlarge on AWS)
RAM: 8GB DDR4
SSD: Needs a DB to hold processed transactions. Above CPU and RAM requirements don’t account for running this database’s hardware. DB size depends on your usage of the network. 20GB seems like a good starting point.