`GET /api/v1/experiments/{id}/results` holds up other requests on the same API process while it computes

已关闭
  • 哪里不对？
#1,738 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

已经有一个关联 PR 被合并了。

  • #1763 来自 @amarkanday —— 已合并

评估

难度
4/5
预计耗时
3-5 天
新手友好度
45/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
python
领域
api, backend

调研方向

Start by tracing the /api/v1/experiments/{id}/results route and how it computes experiment results; the payload does not name the files or tests. Compare it with GET /api/v1/results/{id}, which computes the same results. Done when the experiment results request no longer blocks other requests on the same API process, including flag evaluations.

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

描述

bug

What happens

While the API computes an answer to GET /api/v1/experiments/{id}/results, other requests to the same API process wait until it has
finished, including flag evaluations. On a deployment with one API worker, a results request for a large experiment holds up every other
request for as long as the computation takes.

What should happen

Computing an experiment's results does not hold up other requests on the process.

Notes

  • Priority: medium, before launch (D213: on a one-worker deployment it delays flag evaluation, use cases 1 and 2).
  • GET /api/v1/results/{id} computes the same results; this issue is about the /experiments/{id}/results route.
主要语言
Python
星标
0
派生
4
平均合并
5 小时 36 分钟
30 天内合并 PR
509

环境准备

从这里开始

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

Controlvar/controlvar 的其他 Issue

查看 Controlvar/controlvar 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

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