Never scaling past 1 runner
还没有人认领这个 Issue。
评估
调研方向
Start by reviewing the FLAME.Pool configuration, especially max_concurrency, and the FLAME.FlyBackend settings in runtime.exs. Reproduce the behavior with roughly 30 concurrent FLAME.call invocations and debug logging enabled, then determine why additional runners are not spawned and document or fix the cause.
由索引模型根据 Issue 内容生成。
描述
This could be a misunderstanding on my part but from reading all of the documentation and everything else I can get my hands on I can't figure out why my setup will not utilize more than one runner. Here is my setup
{
FLAME.Pool,
name: Demo.FlamePool,
min: 0,
max: 50,
max_concurrency: 1,
idle_shutdown_after: 30_000,
timeout: 60_000,
log: :debug
}
The backend is configured properly in my runtime.exs file and setup for using Fly as:
config :flame, FLAME.FlyBackend,
token: System.fetch_env!("FLY_API_TOKEN"),
cpu_kind: "performance",
cpus: 4,
memory_mb: 8192
I am using FLAME.call for a function that gets called around 30 times in a short period of time. These are fairly long running functions (some more than the timeout) which I have adjusted the timeout option for to accommodate this and prevent for the runner being terminated. For the life of me I can't figure out why it's only ever choosing to run the jobs on one runner and never spawns more than one. What am I missing here? Any help would be greatly appreciated.
- 主要语言
- Elixir
- 星标
- 1.2k
- 派生
- 68
- PR 合并指标
- 30 天内没有已合并 PR
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
phoenixframework/flame 的其他 Issue
-
难度 4/5 3-5 天 新手友好度 48/100
phoenixframework/flame#86 · 3 个 reaction ·
-
难度 4/5 3-5 天 新手友好度 35/100
phoenixframework/flame#84 · 1 条评论 ·
-
难度 4/5 3-5 天 新手友好度 35/100
phoenixframework/flame#75 · 2 条评论 ·
-
Clean up code_sync tmp files on terminator shutdown可能重新可做 @chrismccord 于 718 天前认领，目前没有进行中的 PR。 未关闭
phoenixframework/flame#70 · 已指派 1 人 ·
-
难度 4/5 3-5 天 新手友好度 35/100
phoenixframework/flame#66 · 1 条评论 ·
查看 phoenixframework/flame 的全部 Issue
相似的 Issue
-
Bug: Table layout and date column are cut off on mobile screens on the Tournaments -> History page未关闭bug
难度 2/5 1-3 小时 新手友好度 74/100
hexlet-codebattle/codebattle#2375 ·
-
Bug
难度 2/5 1-3 小时 新手友好度 68/100
wintermeyer/vutuv#2388 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 74/100
-
Broadcast API docs say to prepend realtime: to the topic, which breaks delivery可能已有人在做 @mandar1045 于 1 天前认领。 未关闭
难度 1/5 1 小时以内 新手友好度 80/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
phoenixframework/phoenix_live_view#4509 ·
维护者通常 1 天内回复