背景:生产 32 天内 >500ms 慢查询从 2.4k/天涨到 1.3 万/天(09-26 尖峰 14.3 万), pg_stat_statements 显示后台工单列表族占 57%、打手端 visible_orders 占 27%; 同时 backend 容器十天从 194MB 涨到 754MB(768MB 限额的 98%),贴顶后整体变慢。 1. 新增迁移 083:work_orders 增加派生列 source_order_amount_fen,并从 material_json.source.orderAmountFen 回填(只认 15 位以内整数,与 JS/SQL 口径一致)。 统计查询原来每行要解析 1.2KB JSON(全表约 132MB)且同一表达式求值两次, 生产实测 3.5~4.4 秒;改走派生列后 COALESCE 短路,未命中列的行才回退 JSON/orders.total_amount, 口径与改造前完全一致。写入点:createWorkOrder / updateWorkOrder 各一处,并加静态守卫。 2. worker_sessions.last_seen_at 从"每个请求都写"改为"5 分钟才写一次": 32 天被写了 3300 万次(占 DB 总时间 2.8%,并堆出 14% 死元组)。仍用一条语句返回鉴权有效性 (EXISTS target AS valid),不能因为不写就让上层 401。 3. 保留策略补上 work_order_events(71.7 万行 / 269MB,此前完全没纳入清理,只增不减), 新增配置 retention.workOrderEventDays(默认 180 天)与 WORK_ORDER_EVENT_RETENTION_DAYS 出口。 4. 内存治理:compose 后端限额 768m→1g 并显式设置 V8 老生代上限(--max-old-space-size=768), 避免贴 cgroup 上限后 GC 抖动;新增每 10 分钟的进程内存快照日志(rss/heapUsed/heapLimit), 用于区分"正常 GC 曲线"与"真泄漏"。 5. 限流桶加 5 万条硬上限:key 里含请求体字段(collect 的 orderNo)时可被构造成高基数, 只按过期清理挡不住内存增长。 验证:后端 530 项单测全绿(新增 11 项,含派生列/会话/保留的静态守卫与解析函数单测)。
153 lines
6.0 KiB
YAML
153 lines
6.0 KiB
YAML
x-json-log-rotation: &json-log-rotation
|
||
driver: json-file
|
||
options:
|
||
max-size: "20m"
|
||
max-file: "5"
|
||
|
||
services:
|
||
postgres:
|
||
image: docker.m.daocloud.io/library/postgres:16-bookworm
|
||
# 开启 pg_stat_statements,便于定位生产环境累计最耗时的 SQL。
|
||
# 内存类参数默认按 4 核 8G 且与其他服务共用的服务器设置(见 .env.server.example)。
|
||
command:
|
||
[
|
||
"postgres",
|
||
"-c",
|
||
"shared_preload_libraries=pg_stat_statements",
|
||
"-c",
|
||
"pg_stat_statements.track=all",
|
||
"-c",
|
||
"log_min_duration_statement=${POSTGRES_LOG_MIN_DURATION_STATEMENT_MS:-500}",
|
||
"-c",
|
||
"shared_buffers=${POSTGRES_SHARED_BUFFERS:-384MB}",
|
||
"-c",
|
||
"effective_cache_size=${POSTGRES_EFFECTIVE_CACHE_SIZE:-4GB}",
|
||
"-c",
|
||
"work_mem=${POSTGRES_WORK_MEM:-16MB}",
|
||
"-c",
|
||
"maintenance_work_mem=${POSTGRES_MAINTENANCE_WORK_MEM:-256MB}",
|
||
]
|
||
restart: unless-stopped
|
||
# 让 PostgreSQL 优雅关闭有足够时间完成检查点;无限制时 OOM 可能拖垮整机。
|
||
mem_limit: ${POSTGRES_MEM_LIMIT:-1.5g}
|
||
cpus: ${POSTGRES_CPUS:-2}
|
||
shm_size: 512mb
|
||
stop_grace_period: 60s
|
||
logging: *json-log-rotation
|
||
environment:
|
||
TZ: ${TZ:-Asia/Shanghai}
|
||
POSTGRES_DB: ${POSTGRES_DB:-order_site}
|
||
POSTGRES_USER: ${POSTGRES_USER:-postgres}
|
||
POSTGRES_PASSWORD: ${POSTGRES_PASSWORD:-postgres}
|
||
healthcheck:
|
||
test:
|
||
[
|
||
"CMD-SHELL",
|
||
"pg_isready -U ${POSTGRES_USER:-postgres} -d ${POSTGRES_DB:-order_site}",
|
||
]
|
||
interval: 5s
|
||
timeout: 5s
|
||
retries: 20
|
||
volumes:
|
||
- postgres_data:/var/lib/postgresql/data
|
||
|
||
backend:
|
||
build:
|
||
context: .
|
||
dockerfile: deploy/docker/backend.Dockerfile
|
||
args:
|
||
# 默认阿里云公共源;阿里云 ECS 内网可设 DEBIAN_MIRROR=mirrors.cloud.aliyuncs.com
|
||
DEBIAN_MIRROR: ${DEBIAN_MIRROR:-mirrors.aliyun.com}
|
||
NPM_REGISTRY: ${NPM_REGISTRY:-https://registry.npmmirror.com}
|
||
restart: unless-stopped
|
||
# 30s 让后端在 SIGTERM 后完成优雅关闭(HTTP 连接收尾 + 数据库连接池释放)。
|
||
# 内存限额 768m → 1g:生产实测十天从重启后的 ~194MB 涨到 754MB(98%),
|
||
# 贴着 cgroup 上限时 V8 会持续 GC 抖动、接口整体变慢(且未必 OOM,所以日志里看不到崩溃)。
|
||
# 服务器 .env 里若仍写着 BACKEND_MEM_LIMIT=768m,会覆盖这里的默认值,需一并调整。
|
||
mem_limit: ${BACKEND_MEM_LIMIT:-1g}
|
||
cpus: ${BACKEND_CPUS:-1.5}
|
||
stop_grace_period: 30s
|
||
env_file:
|
||
- .env
|
||
depends_on:
|
||
postgres:
|
||
condition: service_healthy
|
||
healthcheck:
|
||
test:
|
||
["CMD-SHELL", "curl -fsS http://127.0.0.1:3000/health/ready || exit 1"]
|
||
interval: 5s
|
||
timeout: 5s
|
||
retries: 20
|
||
start_period: 20s
|
||
environment:
|
||
TZ: ${TZ:-Asia/Shanghai}
|
||
PORT: ${BACKEND_PORT:-3000}
|
||
# V8 老生代上限留出余量(限额 1g → 堆 768m):让 GC 在撞上 cgroup 墙之前主动回收,
|
||
# 避免"贴顶后才疯狂 GC"的抖动。native/external 内存与堆外缓冲还需要剩余那部分。
|
||
NODE_OPTIONS: ${BACKEND_NODE_OPTIONS:---max-old-space-size=768}
|
||
HTTP_TRUST_PROXY: ${HTTP_TRUST_PROXY:-1}
|
||
DATABASE_URL: ${DATABASE_URL:-postgres://postgres:postgres@postgres:5432/order_site}
|
||
DATABASE_SSL: ${DATABASE_SSL:-false}
|
||
DATABASE_MAX_CONNECTIONS: ${DATABASE_MAX_CONNECTIONS:-8}
|
||
DATABASE_IDLE_TIMEOUT_MS: ${DATABASE_IDLE_TIMEOUT_MS:-30000}
|
||
DATABASE_CONNECTION_TIMEOUT_MS: ${DATABASE_CONNECTION_TIMEOUT_MS:-5000}
|
||
DATABASE_STATEMENT_TIMEOUT_MS: ${DATABASE_STATEMENT_TIMEOUT_MS:-15000}
|
||
DATA_ROOT: /app/data
|
||
LOG_RETENTION_DAYS: ${LOG_RETENTION_DAYS:-30}
|
||
LOG_MAX_FILE_SIZE_MB: ${LOG_MAX_FILE_SIZE_MB:-20}
|
||
LOG_MAX_FILES: ${LOG_MAX_FILES:-5}
|
||
CLAIM_BASE_URL: ${CLAIM_BASE_URL:-http://localhost/#/claim}
|
||
# 生产图片存储只走阿里云 OSS;MinIO 仅保留在本地开发编排(docker-compose.dev.yml)。
|
||
STORAGE_MODE: ${STORAGE_MODE:-oss}
|
||
STORAGE_ENDPOINT: ${STORAGE_ENDPOINT:-http://minio:9000}
|
||
STORAGE_BUCKET: ${STORAGE_BUCKET:-order-site}
|
||
STORAGE_ACCESS_KEY_ID: ${STORAGE_ACCESS_KEY_ID:-minioadmin}
|
||
STORAGE_SECRET_ACCESS_KEY: ${STORAGE_SECRET_ACCESS_KEY:-minioadmin}
|
||
STORAGE_REGION: ${STORAGE_REGION:-us-east-1}
|
||
STORAGE_MAX_UPLOAD_SIZE_MB: ${STORAGE_MAX_UPLOAD_SIZE_MB:-10}
|
||
STORAGE_OSS_ENDPOINT: ${STORAGE_OSS_ENDPOINT:-}
|
||
STORAGE_OSS_BUCKET: ${STORAGE_OSS_BUCKET:-}
|
||
STORAGE_OSS_ACCESS_KEY_ID: ${STORAGE_OSS_ACCESS_KEY_ID:-}
|
||
STORAGE_OSS_SECRET_ACCESS_KEY: ${STORAGE_OSS_SECRET_ACCESS_KEY:-}
|
||
STORAGE_OSS_REGION: ${STORAGE_OSS_REGION:-oss-cn-hangzhou}
|
||
# ADMIN_SESSION_SECRET / ADMIN_DEFAULT_USERS_JSON 仅走 env_file。
|
||
# 勿在此处用 ${ADMIN_DEFAULT_USERS_JSON} 再注入:JSON 会被 YAML 解析破坏,导致生产校验失败。
|
||
KUASHOU_INDUSTRY_RATE_LIMIT_MAX: ${KUASHOU_INDUSTRY_RATE_LIMIT_MAX:-120}
|
||
logging: *json-log-rotation
|
||
volumes:
|
||
- ./apps/backend/data:/app/data
|
||
|
||
web:
|
||
build:
|
||
context: .
|
||
dockerfile: deploy/docker/frontend.Dockerfile
|
||
args:
|
||
APP_DOMAIN: ${APP_DOMAIN:-localhost}
|
||
VITE_WORKER_SITE_URL: ${WORKER_SITE_ADDR:-https://worker.khhao.com}
|
||
ALPINE_MIRROR: ${ALPINE_MIRROR:-mirrors.aliyun.com}
|
||
NPM_REGISTRY: ${NPM_REGISTRY:-https://registry.npmmirror.com}
|
||
restart: unless-stopped
|
||
mem_limit: ${WEB_MEM_LIMIT:-256m}
|
||
cpus: ${WEB_CPUS:-0.5}
|
||
stop_grace_period: 20s
|
||
logging: *json-log-rotation
|
||
depends_on:
|
||
backend:
|
||
condition: service_healthy
|
||
ports:
|
||
- "80:80"
|
||
- "443:443"
|
||
environment:
|
||
TZ: ${TZ:-Asia/Shanghai}
|
||
APP_DOMAIN: ${APP_DOMAIN:-localhost}
|
||
CADDY_SITE_ADDR: ${CADDY_SITE_ADDR:-http://localhost}
|
||
WORKER_SITE_ADDR: ${WORKER_SITE_ADDR:-https://worker.khhao.com}
|
||
volumes:
|
||
- caddy_data:/data
|
||
- caddy_config:/config
|
||
|
||
volumes:
|
||
postgres_data:
|
||
caddy_data:
|
||
caddy_config:
|