Doesn't work for datacenters.
Doesn't work for datacenters. Also is implemented with round-robin DNS to nodes (1-N, check X-Forwarded-For) in each AZ, which then handle balancing. Also worth noting that unless you turn on cross-region balancing, if an AZ doesn't have a node in it and the RR DNS points them at that AZ, they'll be turned away. Additionally, without it you need to scale by multiples of AZs you run in otherwise you'll have unbalanced traffic. On another note, I've always been curious if they're just abstractions around HAproxy at the per-node level.
Posted by Xorlev on May 28, 2014, 6:51 PM
Tags
Related issues
- (1) Because it doesn't actually solve the problem.
- Every time fossil comes up, I hear this same issue - "why is there no rebase?" And honestly, I've never been able to get this argument.
- My biggest problem with running local LLMs on my M4 Max/128GB RAM is the prefill latency.
- Biggest problem with httpx I see is authors sanity https://github.com/encode/httpx/discussions/3784 .
- There aren't many situations today that make one think: Why doesn't this business have a website?
- > IAM can stay MS That's leaving the most critical component still with a US company.
Raise real-world problems, find people facing the same issue, and discuss solutions.9,500 issues0 comments
hackernews (Network)
(1) Because it doesn't actually solve the problem.
Every time fossil comes up, I hear this same issue - "why is there no rebase?" And honestly, I've never been able to get this argument.
My biggest problem with running local LLMs on my M4 Max/128GB RAM is the prefill latency.
Biggest problem with httpx I see is authors sanity https://github.com/encode/httpx/discussions/3784 .
There aren't many situations today that make one think: Why doesn't this business have a website?
> IAM can stay MS That's leaving the most critical component still with a US company.
I am very petty about this one bug and have a very old axe to grind that this reminded me of!
Not just the edge router.
Doesn't work for datacenters.
Doesn't work for datacenters. Also is implemented with round-robin DNS to nodes (1-N, check X-Forwarded-For) in each AZ, which then handle balancing. Also worth noting that unless you turn on cross-region balancing, if an AZ doesn't have a node in it and the RR DNS points them at that AZ, they'll be turned away. Additionally, without it you need to scale by multiples of AZs you run in otherwise you'll have unbalanced traffic. On another note, I've always been curious if they're just abstractions around HAproxy at the per-node level.
Comments (0)
No comments yet. Start the discussion.