Published scale evidence: a load test with a stated method

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

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
15/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
aws, docker-compose, postgresql

调研方向

Start from the four hot paths named in the issue: GET /api/v1/feature-flags/evaluate/{key}, POST /api/v1/tracking/assign, POST /api/v1/tracking/track and /batch, and the SDK ruleset. Read the Compose stack and, if reachable, the CDK stack to record the deployment shape, then choose a load generator and a method. Done means a committed script, a measured run with RPS, p50/p95/p99 and error rate, and a docs page stating setup and limits. Any billed cloud run needs the founder's approval first.

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

描述

enhancement post-launch

Events are stored in PostgreSQL, and no throughput figures are published. A team evaluating a self-hosted platform asks "will it hold my traffic?" before anything else, and today there is no answer to point to.

Wanted before launch (founder, 2026-11-02): published scale evidence, a load test with a stated method.

  • The hot paths an integrating app drives: flag evaluation (GET /api/v1/feature-flags/evaluate/{key}), assignment (POST /api/v1/tracking/assign), event tracking (POST /api/v1/tracking/track and /batch), and the SDK ruleset.
  • A stated setup: the deployment shape (the Compose stack, and if possible the CDK stack), instance sizes, data volume already in the database, concurrency, duration, and where the load generator runs.
  • Results as requests per second and latency percentiles (p50, p95, p99) and the error rate, with the point where it stops keeping up and what saturates first.
  • The script and the method committed, so anyone can repeat it; a docs page that states the numbers, the setup and what was not measured.
  • Numbers come from a measured run, never estimated; a single wall-clock timing is not a gate.

Where it runs (a laptop, a CI runner, or a billed cloud environment) is decided in the plan; anything that bills waits for the founder at that moment.

主要语言
Python
星标
0
派生
4
平均合并
6 小时 5 分钟
30 天内合并 PR
453

环境准备

从这里开始

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

Controlvar/controlvar 的其他 Issue

查看 Controlvar/controlvar 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

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