[BUG] grpc server job selection algorithm can starve clients when multiple clients continuously submit

未关闭
#2,210 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
30/100
Issue 类型
缺陷
描述清晰度
需要澄清
活跃度
活跃
技术栈
grpc
领域
api, backend

调研方向

The issue describes job scheduling in the gRPC server but names no source files or tests. Start by locating the server’s slot selection and job dispatch code, then inspect its scheduling tests. Done when waiting jobs are served fairly under continuous submissions and the legacy REST FIFO behavior remains unaffected.

由索引模型根据 Issue 内容生成。

描述

bug

Workaround (26.10 proxy and direct gRPC in 26.08+). The server runs jobs by scanning slots from slot 0, not in arrival order. A client that submits again as soon as its job finishes can take the lowest free slot and run ahead of jobs already waiting. Those waiting jobs can stay queued while other clients complete many times.

Keep at most one job in flight per worker. Use a single submitter, or a shared lock or FIFO in your
application, and submit the next job only after the current result is retrieved. With one worker,
extra jobs sitting in the server queue do not add throughput.

A one-shot batch of at most 100 jobs is fine if nothing else is submitted until that batch finishes
. The server rejects anything beyond 100 in flight with Job queue full (HTTP 500 through the proxy,
RESOURCE_EXHAUSTED on gRPC).

The legacy REST server is unaffected: it dispatches from a FIFO.

主要语言
Cuda
星标
1.1k
派生
255
平均合并
1 天 22 小时
30 天内合并 PR
102

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

NVIDIA/cuopt 的其他 Issue

查看 NVIDIA/cuopt 的全部 Issue

相似的 Issue

更多 Backend & API Design Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。