infra: agent backend cannot scale beyond a few concurrent users
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 30/100
- Issue 类型
- 功能
- 描述清晰度
- 需要澄清
- 活跃度
- 冷清
- 技术栈
- postgresql, python, redis, sqlite, typescript
调研方向
Start with apps/agent/main.py, apps/agent/src/bounded_memory_saver.py, render.yaml, and apps/app/src/app/api/copilotkit/route.ts; reproduce the concurrency failure described in #63 before choosing a phase. The work is done only when the selected scaling, persistence, backpressure, or load-testing goals are implemented and verified at the stated target concurrency.
由索引模型根据 Issue 内容生成。
描述
Problem
The agent backend runs on a single uvicorn worker process with an in-memory checkpointer on a 512MB Render starter instance. This is a global bottleneck — not per-user. All concurrent users share the same event loop, the same memory pool, and the same 200-thread checkpoint limit.
Currently the app breaks at ~3 concurrent connections (#63). At production scale (100-1000 users), it would be effectively unusable.
Architecture bottlenecks
1. Single worker process
- uvicorn runs with 1 worker (default) — all requests share one Python event loop
- Each GPT-5.4 visualization call takes 10-30s
- LangGraph has synchronous sections that block the event loop
- Throughput: ~2-6 visualization requests/minute
2. In-memory checkpointer (BoundedMemorySaver)
- All conversation state stored in RAM — shared global pool of 200 threads
- FIFO eviction: after 200 conversations across ALL users, oldest threads are silently deleted
- Users lose conversation context mid-session with no error
- Not thread-safe — designed for single-process async only
- On 512MB starter plan, memory pressure builds well before 200 threads
3. No backpressure or error surfacing
- When the backend is saturated, requests hang silently — no timeout, no error, no retry
- Frontend shows no indication that the agent is overloaded
- Health check at
/healthreturns 200 even when the event loop is blocked
Scale projections
| Concurrent users | Behavior |
|---|---|
| 1-5 | Works fine |
| 10-20 | Noticeable latency, requests queue |
| 50+ | Requests timeout, SSE connections drop |
| 100+ | Effectively down, health checks fail, Render restarts |
Proposed solution
Phase 1 — Quick wins (config changes only)
- Add
--workers 4to uvicorn startCommand inrender.yaml— multiplies throughput ~4x - Upgrade agent service from starter (512MB) to standard (1GB+) in
render.yaml - Enable rate limiting (
RATE_LIMIT_ENABLED=true) with reasonable limits (e.g. 20 req/min per IP)
Phase 2 — Persistent checkpointer
- Replace
BoundedMemorySaverwith PostgreSQL or SQLite async checkpointer - Conversation state survives restarts and doesn't consume RAM
- No more silent thread eviction — threads persist until explicitly cleaned up
- Render already supports managed Postgres — can add as a service in
render.yaml
Phase 3 — Error handling and backpressure
- Add frontend timeout — show error after ~30s of no response instead of hanging forever
- Add backend concurrency limit — return 503 "busy" when at capacity rather than queuing indefinitely
- Add connection health monitoring — detect dropped SSE connections and surface to user
- Reuse thread IDs per browser tab (
sessionStorage) to avoid creating unnecessary threads
Phase 4 — Horizontal scaling
- Use Gunicorn with uvicorn workers for proper process management
- Verify Render auto-scaling (1-3 instances) works correctly with persistent checkpointer
- Add Redis or Postgres for shared state across instances
- Load test at target concurrency (100+ users) to validate
Related issues
- #63 — Agent stops responding after multiple concurrent tabs (symptom of this)
- #58 — Quality regression (long-running visualization calls exacerbate the single-worker bottleneck)
- #62 — Planning step before visualization (adds an extra round-trip, making concurrency even more critical)
Key files
apps/agent/main.py— uvicorn config, BoundedMemorySaver(max_threads=200)apps/agent/src/bounded_memory_saver.py— FIFO eviction logicrender.yaml— Render service config (starter plan, no worker config)apps/app/src/app/api/copilotkit/route.ts— Frontend → agent connection
- 主要语言
- TypeScript
- 星标
- 1.6k
- 派生
- 202
- PR 合并指标
- 30 天内没有已合并 PR
贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
CopilotKit/OpenGenerativeUI 的其他 Issue
-
bug
难度 2/5 1-3 小时 新手友好度 72/100
-
enhancement
难度 2/5 1-3 小时 新手友好度 72/100
-
难度 4/5 3-5 天 新手友好度 48/100
CopilotKit/OpenGenerativeUI#87 · 2 条评论 ·
-
难度 5/5 一周以上 新手友好度 35/100
-
难度 4/5 3-5 天 新手友好度 45/100
查看 CopilotKit/OpenGenerativeUI 的全部 Issue
相似的 Issue
-
Type/Bug
难度 2/5 1-3 小时 新手友好度 78/100
OpenNSW/nsw-srilanka#497 ·
-
难度 2/5 1-3 小时 新手友好度 72/100
0xMiden/bridge-portal#132 ·
-
react-doctor severity:warning tech-debt
难度 1/5 1 小时以内 新手友好度 88/100
digidem/comapeo-cloud-app#403 ·
-
难度 2/5 1-3 小时 新手友好度 72/100
-
难度 2/5 1-3 小时 新手友好度 78/100