In this case I’m doing capacity planning to verify whether the nodes I’ve deployed are capable enough to sustain the workloads of POA bootnode and validator roles. If you see CPU spending too much time above 70% you need to scale-up your node. Our workloads are currently clearly not CPU bound, though that may change as more people run DApps on the POA networks.
Same goes for I/O - if you see IOPS trending up into double digits, we should explore faster storage options for the node. Since blockchain nodes are I/O heavy workloads, SSD is always recommended for the validator node. With the bootnode using an HDD should be fine. Luckily, Azure gives you a very inexpensive B1s instance that also has SSD, so I won’t say no to good freebies .
Network ingress/egress is more of a cost factor as we pay for all the network activities crossing the datacenter boundaries, though so far they don’t seem significant enough. Local storage I/O footprint on the other hand has been increasingly monotonically with a 3x spike at the end of January on both my Sokol bootnode and validator node, so I’m watching that metric closely.
Does that help answer your question?