3 ms·

Why do we keep coming up with these bizarre ways to try and make this work? It is the normal operating mode of an internet connected server to send traffic to

Why do we keep coming up with these bizarre ways to try and make this work? It is the normal operating mode of an internet connected server to send traffic to the internet - often even 100% of the time! It is the normal operating mode of drinks at a restaurant to be drank by the person while there, and maybe one refill for the road. Trying to liken "Using the 'Unlimited' 1gbps port that was advertised "to "Refilling a cup and dumping it into a garbage bag" is ludicrous. I don't understand why people are doing mental gymnastics to defend a bad advertising practice.

Volundr 4y ago
> It is the normal operating mode of an internet connected server to send traffic to the internet - often even 100% of the time! It is? I've been admining servers for a long time and I've never run one using 100% of it's upload bandwidth 100% of the time. I've never even run one at 80%. Being that near capacity means your service is about to fall over. Frankly for most services it's probably flagging.
- cthalupa 4y ago
  There are plenty of workloads where 20% slack in the workload would result in massive (both relative and in absolute terms) additional costs. In these sorts of workloads, it's incredibly common to run any individual server in the fleet very close to maximum capacity. And even if any individual workload isn't, virtualization and containers letting you bin-pack servers makes it even more common.
  - Volundr 4y ago
    Such as? Sure if you are operating on massive scale or have a remarkably steady load that 20% margin might be feasible, but that's the exception not the rule. Especially for a lone piece of physical hardware that can't scale up/down.
    - eropple 4y ago
      I'd be interested in an example of this, too, because I've been doing this for a while and I can't think of many--particularly in a modern, scalable environment (because Hetzner's APIs aren't great but you absolutely can scale automatically in their environment if you want to).

Volundr 4y ago

> It is the normal operating mode of an internet connected server to send traffic to the internet - often even 100% of the time! It is? I've been admining servers for a long time and I've never run one using 100% of it's upload bandwidth 100% of the time. I've never even run one at 80%. Being that near capacity means your service is about to fall over. Frankly for most services it's probably flagging.

cthalupa 4y ago
There are plenty of workloads where 20% slack in the workload would result in massive (both relative and in absolute terms) additional costs. In these sorts of workloads, it's incredibly common to run any individual server in the fleet very close to maximum capacity. And even if any individual workload isn't, virtualization and containers letting you bin-pack servers makes it even more common.
- Volundr 4y ago
  Such as? Sure if you are operating on massive scale or have a remarkably steady load that 20% margin might be feasible, but that's the exception not the rule. Especially for a lone piece of physical hardware that can't scale up/down.
  - eropple 4y ago
    I'd be interested in an example of this, too, because I've been doing this for a while and I can't think of many--particularly in a modern, scalable environment (because Hetzner's APIs aren't great but you absolutely can scale automatically in their environment if you want to).