4 ms·

It would be helpful if the author specified what the price difference actually was here at the end of the day - their initial cost was $3,500/mo but they don't

It would be helpful if the author specified what the price difference actually was here at the end of the day - their initial cost was $3,500/mo but they don't mention how much they pay now after changing instance types.

aledalgrande 7y ago
> In case of this particular deployment, these pods will change between idle/ active state multiple times every minute and spend 70%+ in idle state. I would guess he more or less halved the price if you suppose at any minute 70% of the pods are idle, but they still consume > 0 resources, and the price per vcpu didn't change, like he said. Then you also have the overhead of running the Kubernetes processes which is cut to about 1/100th lowering the price further. Not real numbers, but gives you an idea.
auslander 7y ago
I wonder what would be the cost without k8s setup and no containers at all, pure compute nodes. I bet my last socks twice less, at least.
- neurostimulant 7y ago
  With $3500/mo budget you could get 15 AMD servers on Hetzner, each with 32 cores and 128gb of RAM. You won't get autoscaling and other nice stuff available in other cloud providers, but nothing beat dedicated servers in term of price vs performance ratio.
  - auslander 7y ago
    I meant it in cloud, AWS/GCP, because devops, lol. With autoscaling.
  - Wintereise 7y ago
    Commoditized cloud is basically paying a company to run your ops for you. Let's not forget that you'd also have to pay at least 3 (8 hours per shift, not accounting for weekends) people to ensure 24/7 service availability through those 15 Hetzner nodes. AWS/GCP/Azure et al make it so you generally don't need to worry about the infrastructure part of the problem. Everything else still applies though.
    - neurostimulant 7y ago
      > Let's not forget that you'd also have to pay at least 3 (8 hours per shift, not accounting for weekends) people to ensure 24/7 service availability through those 15 Hetzner nodes. This is true if you run your own datacenter, but dedicated server providers typically monitor their servers and immediately intervene if they detect any connectivity/network issue (which is outside our control even if we use cloud providers like AWS). For individual server failure (disk issue, etc), how you handle failure condition on dedicated servers is not much different than handling failure on cloud servers (remove the bad server from the cluster, re-image a new server and join it to the cluster). The main difference is provisioning new physical server is not instant, so you'll need to plan ahead and either have some spares or slightly over-provision your cluster (so you can take down a few nodes without degrading your service). You can do this automatically or manually, not much different than using cloud servers. Using dedicated servers is not as scary as what people thought it would be.
    - auspex 7y ago
      Except for security. You still have to.worry about that part of the infrastructure.
- ianamartin 7y ago
  Yeah, basically this.

aledalgrande 7y ago

> In case of this particular deployment, these pods will change between idle/ active state multiple times every minute and spend 70%+ in idle state. I would guess he more or less halved the price if you suppose at any minute 70% of the pods are idle, but they still consume > 0 resources, and the price per vcpu didn't change, like he said. Then you also have the overhead of running the Kubernetes processes which is cut to about 1/100th lowering the price further. Not real numbers, but gives you an idea.

auslander 7y ago

I wonder what would be the cost without k8s setup and no containers at all, pure compute nodes. I bet my last socks twice less, at least.

neurostimulant 7y ago
With $3500/mo budget you could get 15 AMD servers on Hetzner, each with 32 cores and 128gb of RAM. You won't get autoscaling and other nice stuff available in other cloud providers, but nothing beat dedicated servers in term of price vs performance ratio.
- auslander 7y ago
  I meant it in cloud, AWS/GCP, because devops, lol. With autoscaling.
- Wintereise 7y ago
  Commoditized cloud is basically paying a company to run your ops for you. Let's not forget that you'd also have to pay at least 3 (8 hours per shift, not accounting for weekends) people to ensure 24/7 service availability through those 15 Hetzner nodes. AWS/GCP/Azure et al make it so you generally don't need to worry about the infrastructure part of the problem. Everything else still applies though.
  - neurostimulant 7y ago
    > Let's not forget that you'd also have to pay at least 3 (8 hours per shift, not accounting for weekends) people to ensure 24/7 service availability through those 15 Hetzner nodes. This is true if you run your own datacenter, but dedicated server providers typically monitor their servers and immediately intervene if they detect any connectivity/network issue (which is outside our control even if we use cloud providers like AWS). For individual server failure (disk issue, etc), how you handle failure condition on dedicated servers is not much different than handling failure on cloud servers (remove the bad server from the cluster, re-image a new server and join it to the cluster). The main difference is provisioning new physical server is not instant, so you'll need to plan ahead and either have some spares or slightly over-provision your cluster (so you can take down a few nodes without degrading your service). You can do this automatically or manually, not much different than using cloud servers. Using dedicated servers is not as scary as what people thought it would be.
  - auspex 7y ago
    Except for security. You still have to.worry about that part of the infrastructure.
ianamartin 7y ago
Yeah, basically this.