perf(worker-platform): 排行榜公共缓存与抢单短路,压制 8.5s 慢查询脉冲
- 排行榜:Top 10 改为按 period 全局共享缓存(TTL 30s),SQL 传 currentWorkerId=0; 个人单数解耦为 assigned_worker_id 精准索引查询(TTL 15s),未上榜展示「暂未上榜」, 消除「每个打手一份缓存」导致的 8.5 秒全表聚合穿透; - 抢单短路:新增 work-order-grab-guard,对已关闭工单打 10s 进程内标记,命中直接 409; publishWorkOrderRealtimeChange 统一作废标记,避免撤单/超时重开/重新发布后误杀正常抢单; - 我的订单:默认排序也走「先取 id 再批量回表」的延迟分页,避免宽列 material_json 参与排序; - 文档:新增生产 CPU 波动分析报告,慢查询数字按 6,235 行日志实测重算,并标注修复状态与验收口径。 验证:typecheck / check:sql / eslint / prettier 通过;后端 npm test 914 项(910 pass、4 skip、0 fail)。
This commit is contained in:
@@ -435,12 +435,11 @@ export async function listWorkOrders({
|
||||
const effectiveOrderBy = pinnedFirst ? `wo.pinned_at DESC NULLS LAST, ${orderBy}` : orderBy
|
||||
params.push(pageSize, offset)
|
||||
|
||||
// 打手端「我的订单」的排序是表达式(依赖打手参数与拼单表),**没有索引能支撑**,
|
||||
// 规划器只能把该打手全部可见单连同宽列(含 1.2KB 的 material_json)物化后排序。
|
||||
// 生产实测:名下 6600 单的打手首访 1112ms、每次读约 60MB(列表缓存 2 秒一失效,
|
||||
// 所以这个代价每分钟会重复付好几次)。这里改成"先只取当前页的 id,再按 id 取详情":
|
||||
// 排序阶段只带窄列,宽列只回表 20 行。语义(行集、顺序、总数)完全不变。
|
||||
if (sort === 'worker_claimed_at_desc' && workerSharingId && !pinnedFirst) {
|
||||
// 打手端「我的订单」:不论是按接单时间排序还是按 id 默认排序,
|
||||
// 都走"先只取当前页的 id,再按 id 批量取详情"的延迟分页模式。
|
||||
// 避免宽列(含 1.2KB 的 material_json)在匹配和排序时全表物化。
|
||||
// 语义(行集、顺序、总数)完全不变,大幅降低内存与数据库缓冲读。
|
||||
if (workerSharingId && !pinnedFirst) {
|
||||
const idsResult = await query<{ id: number }>(
|
||||
`SELECT wo.id
|
||||
FROM work_orders wo
|
||||
|
||||
@@ -29,6 +29,62 @@ export async function countWorkerAcceptedOrders(workerId: number | string): Prom
|
||||
return Number(result.rows[0]?.total || 0)
|
||||
}
|
||||
|
||||
/** 按周期轻量统计单打手完成单数(走 assigned_worker_id 精准索引,耗时 1~2ms,避免全表扫描) */
|
||||
export async function countWorkerAcceptedOrdersByPeriod(
|
||||
workerId: number | string,
|
||||
period: 'all' | 'daily' = 'all',
|
||||
): Promise<number> {
|
||||
const normalizedWorkerId = Number(workerId)
|
||||
if (!normalizedWorkerId) return 0
|
||||
const dailyOnly = period === 'daily'
|
||||
const result = await query<{ total: number }>(
|
||||
`
|
||||
WITH leaderboard_day AS (
|
||||
SELECT
|
||||
date_trunc('day', CURRENT_TIMESTAMP AT TIME ZONE 'Asia/Shanghai')
|
||||
AT TIME ZONE 'Asia/Shanghai' AS starts_at
|
||||
)
|
||||
SELECT COUNT(DISTINCT order_key)::int AS total
|
||||
FROM (
|
||||
SELECT
|
||||
COALESCE(
|
||||
'order:' || NULLIF(wo.order_id::text, ''),
|
||||
'platform_order:' || NULLIF(BTRIM(wo.platform_order_id), ''),
|
||||
'work_order:' || wo.id::text
|
||||
) AS order_key
|
||||
FROM work_orders wo
|
||||
CROSS JOIN leaderboard_day
|
||||
WHERE wo.assigned_worker_id = $1
|
||||
AND wo.status = 'accepted'
|
||||
AND (
|
||||
$2::boolean = false
|
||||
OR (wo.accepted_at >= leaderboard_day.starts_at AND wo.accepted_at < leaderboard_day.starts_at + INTERVAL '1 day')
|
||||
)
|
||||
|
||||
UNION
|
||||
|
||||
SELECT
|
||||
COALESCE(
|
||||
'order:' || NULLIF(wo.order_id::text, ''),
|
||||
'platform_order:' || NULLIF(BTRIM(wo.platform_order_id), ''),
|
||||
'work_order:' || wo.id::text
|
||||
) AS order_key
|
||||
FROM work_order_shares wos
|
||||
INNER JOIN work_orders wo ON wo.id = wos.work_order_id
|
||||
CROSS JOIN leaderboard_day
|
||||
WHERE wos.worker_id = $1
|
||||
AND wos.status = 'accepted'
|
||||
AND (
|
||||
$2::boolean = false
|
||||
OR (wos.accepted_at >= leaderboard_day.starts_at AND wos.accepted_at < leaderboard_day.starts_at + INTERVAL '1 day')
|
||||
)
|
||||
) AS completed_orders
|
||||
`,
|
||||
[normalizedWorkerId, dailyOnly],
|
||||
)
|
||||
return Number(result.rows[0]?.total || 0)
|
||||
}
|
||||
|
||||
export async function listWorkerCompletionLeaderboard(input: {
|
||||
limit: number
|
||||
currentWorkerId: number
|
||||
|
||||
Reference in New Issue
Block a user