Issue with the "Load Balancing" doc RE: in-region loadbalancing
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 1/5
- 预计耗时
- 1 小时以内
- 新手友好度
- 35/100
- Issue 类型
- 文档
- 描述清晰度
- 基本清楚
- 活跃度
- 停滞
调研方向
打开 reference/load-balancing.html.md 并检查引用的 Load Balancing 示例。首先与 networking 团队确认预期的 Load Balancing 行为，然后更新示例以匹配该行为。当文档中 soft_limit 和 hard_limit 的路由顺序准确无误时，即表示完成。
由索引模型根据 Issue 内容生成。
描述
I found an issue with this document.
Title: Load Balancing
Location: https://fly.io/docs/reference/load-balancing/
Source: https://github.com/superfly/docs/blob/main/reference/load-balancing.html.md
Describe the issue
The Proxy as currently configured will avoid routing requests outside a given region until all machines in that region are over their hard_limit. The current examples state that we'll start routing to nearby regions once all machines in them are over the soft limit. This is incorrect!
This example section needs updating:
In this contrived example, all of the users are currently in Amsterdam, so the traffic is arriving at one of the Fly.io edges in Amsterdam. Here’s what happens as the number of concurrent HTTP requests from users in Amsterdam increases:
60 concurrent requests: Requests are divided evenly between the 3 Machines in the ams region. Closeness of the worker and edge will determine which of the 3 Machines each request goes to.
61+ concurrent requests: 60 of those requests will be sent to the 3 Machines in the ams region and the rest will be sent to the closest Machines in other regions.
200+ concurrent requests: All Machines are at their soft_limit, so Fly Proxy will start routing requests to the ams Machines again. For example, the 201st concurrent request will go to a Machine in the ams region that is currently at its soft_limit.
250 concurrent requests: All Machines are at their hard_limit. The 251st concurrent request will get queued by Fly Proxy until a Machine is below its hard_limit.
Addtional info
Doublechecking with the networking team to ensure that the change from what's documented was intentional. Once that's confirmed I can make a PR to update this
- 主要语言
- MDX
- 星标
- 128
- 派生
- 1.1k
- 平均合并
- 20 小时 51 分钟
- 30 天内合并 PR
- 81
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 没有贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
superfly/docs 的其他 Issue
-
documentation
难度 1/5 1 小时以内 新手友好度 85/100
维护者通常 1 天内回复
-
documentation
难度 1/5 1 小时以内 新手友好度 74/100
维护者通常 1 天内回复
-
documentation
难度 2/5 1-3 小时 新手友好度 62/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 68/100
维护者通常 1 天内回复
-
documentation
难度 1/5 1 小时以内 新手友好度 85/100
维护者通常 1 天内回复
相似的 Issue
-
content triage
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 88/100
维护者通常 1 天内回复
-
b4b docs-loc:codebase docs:minor-content-fix documentation
难度 2/5 1-3 小时 新手友好度 65/100
维护者通常 1 天内回复
-
graph-2026-11-simplify
难度 2/5 1-3 小时 新手友好度 72/100
sequant-io/sequant#1650 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 78/100