|
|
|
|
|
by cb22
1346 days ago
|
|
I too was initially put off by those requirements. Now we run our Nomad server on a single t3.medium instance that sits at a 0.1 15 minute load average and has ~500MB of RAM used. This manages about 100 client nodes. No need for a cluster since we don't need high availability on our control plane, and there's no actual state stored there that isn't created from our CI pipeline. |
|
Nomad servers could start with 300mhz, 100mb of memory, and eMMC storage and run a RaspberryPI cluster just fine. Our most important resource guidance is all the way over in our Monitoring docs!
> Nomad servers' memory, CPU, disk, and network usage all scales linearly with cluster size and scheduling throughput.
https://developer.hashicorp.com/nomad/docs/operations/monito...
Any cluster can start with 300mhz and 100mb as long as they monitor usage and scale appropriately.
We're going to try to update our Requirements docs to add this nuance and guidance on how to calculate requirements based on projected load. We recently spent some time improving our heartbeat docs, and I think the approach we took there will serve us well for system requirements: https://developer.hashicorp.com/nomad/docs/configuration/ser...