执行器性能优化

本文引用的文件
- src/executor/php_cgi_executor.v - src/executor/socket_worker_executor.v - src/upstream/transport/fastcgi.v - src/upstream/transport/worker_pool.v - src/executor/inproc_vjsx_lifecycle.v - src/executor/inproc_vjsx_lane_pool.v - src/executor/inproc_vjsx_host_lifecycle.v - src/executor/inproc_vjsx_lane_worker_runtime.v - src/executor/inproc_vjsx_lane_wakeup_runtime.v - src/executor/inproc_vjsx_host_shutdown.v - docs/EXECUTOR_MODES.md - config/vhttpd.example.toml - config/vhttpd.vjsx.example.toml - articles/11-observability.md

引言

本指南聚焦 vhttpd 的执行器性能优化，覆盖 PHP Worker 与 VJSX 两种执行模式。内容涵盖： - Worker 池大小、进程间通信、内存管理与超时配置 - CGI 模式与 Worker 模式的差异及适用场景 - 生命周期管理（启动预热、优雅关闭、故障恢复） - 资源隔离、负载均衡与弹性扩缩容方案与最佳实践

项目结构

vhttpd 提供两类内置执行器： - PHP 模式：通过 Unix Socket 与外部 PHP Worker 通信（支持 FastCGI 与自定义 Worker 协议） - VJSX 模式：进程内嵌入执行，基于“车道”并发模型

graph TB
subgraph "HTTP 入口"
H["HTTP 请求"]
end
subgraph "PHP 执行器"
PWE["SocketWorkerExecutor<br/>php-worker 协议"]
PCGI["PhpCgiExecutor<br/>FastCGI 协议"]
WP["ManagedWorkerPool<br/>进程池管理"]
FC["FastCgiCodec<br/>协议编解码"]
end
subgraph "VJSX 执行器"
VL["InProcVjsxExecutor<br/>生命周期/调度"]
LP["Lane Pool<br/>轮询选择"]
LW["Lane Worker Runtime<br/>任务循环"]
HL["Host Lifecycle<br/>模块加载/绑定"]
SH["Shutdown<br/>优雅关闭"]
end
H --> PWE
H --> PCGI
PWE --> WP
PCGI --> FC
H --> VL
VL --> LP
VL --> LW
VL --> HL
VL --> SH

图示来源 - src/executor/socket_worker_executor.v:1-157 - src/executor/php_cgi_executor.v:1-118 - src/upstream/transport/worker_pool.v:1-219 - src/upstream/transport/fastcgi.v:1-386 - src/executor/inproc_vjsx_lifecycle.v:1-155 - src/executor/inproc_vjsx_lane_pool.v:1-144 - src/executor/inproc_vjsx_lane_worker_runtime.v:1-87 - src/executor/inproc_vjsx_host_lifecycle.v:1-193 - src/executor/inproc_vjsx_host_shutdown.v:1-73

章节来源 - docs/EXECUTOR_MODES.md:1-136

核心组件

PHP Worker 执行器（SocketWorkerExecutor）
负责通过 Unix Socket 与 PHP Worker 进程通信，支持 HTTP、流式、WebSocket 等分发
使用 WorkerFrameCodec/WorkerHttpRequestCodec 进行帧编解码
PHP CGI 执行器（PhpCgiExecutor）
通过 FastCGI 协议与 php-cgi 交互，仅支持 HTTP 响应
VJSX 执行器（InProcVjsxExecutor）
进程内执行，按线程数创建“车道”，采用轮询+健康检查的调度策略
包含 Host 生命周期管理、任务派发、唤醒机制与优雅关闭

章节来源 - src/executor/socket_worker_executor.v:1-157 - src/executor/php_cgi_executor.v:1-118 - src/executor/inproc_vjsx_lifecycle.v:1-155

架构总览

下图展示 PHP 与 VJSX 两条路径的关键交互与数据流。

sequenceDiagram
participant C as "客户端"
participant S as "vhttpd 服务"
participant P as "SocketWorkerExecutor"
participant W as "PHP Worker 进程"
participant F as "FastCgiCodec"
participant G as "PhpCgiExecutor"
participant J as "InProcVjsxExecutor"
participant L as "Lane 池"
participant R as "Lane 工作协程"
C->>S : "HTTP 请求"
alt "PHP Worker 模式"
S->>P : "dispatch_http()"
P->>W : "连接 Unix Socket + 发送帧"
W-->>P : "返回响应/流/上游计划"
P-->>S : "HttpLogicDispatchOutcome"
S-->>C : "响应"
else "PHP CGI 模式"
S->>G : "dispatch_http()"
G->>F : "编码 FastCGI 请求"
F-->>G : "解析响应"
G-->>S : "HttpLogicDispatchOutcome"
S-->>C : "响应"
else "VJSX 模式"
S->>J : "选择车道"
J->>L : "select_next_lane()/acquire_next_lane()"
L-->>J : "返回可用 Lane"
J->>R : "投递任务到 Lane 队列"
R-->>J : "回调结果"
J-->>S : "处理完成"
S-->>C : "响应"
end

图示来源 - src/executor/socket_worker_executor.v:43-95 - src/executor/php_cgi_executor.v:42-82 - src/upstream/transport/fastcgi.v:79-249 - src/executor/inproc_vjsx_lane_pool.v:5-30 - src/executor/inproc_vjsx_lane_worker_runtime.v:7-86

详细组件分析

PHP Worker 执行器（SocketWorkerExecutor）

职责
选择目标 Unix Socket，设置读超时，编码请求帧并写入
读取首帧判断为普通响应、流或上游计划，分别返回不同结果类型
支持 WebSocket 会话打开与事件分发
关键流程
选择 socket -> 连接 -> 写帧 -> 读首帧 -> 分支处理 -> 释放连接

flowchart TD
Start(["进入 dispatch_http"]) --> Select["选择后端 Socket"]
Select --> Connect["建立连接并设置读超时"]
Connect --> Encode["编码请求帧"]
Encode --> Write["写入请求帧"]
Write --> ReadFirst["读取首帧"]
ReadFirst --> IsStream{"是否流式?"}
IsStream --> |是| ReturnStream["返回流式结果"]
IsStream --> |否| IsPlan{"是否上游计划?"}
IsPlan --> |是| ReturnPlan["返回上游计划"]
IsPlan --> |否| DecodeResp["解码 JSON 响应"]
DecodeResp --> Close["关闭连接并释放"]
Close --> End(["返回响应结果"])

图示来源 - src/executor/socket_worker_executor.v:43-95

章节来源 - src/executor/socket_worker_executor.v:1-157

PHP CGI 执行器（PhpCgiExecutor）

职责
将 HTTP 请求转换为 FastCGI 请求帧，发送至 php-cgi 进程
解析 stdout/stderr 并构造 WorkerResponse
关键流程
选择 socket -> 连接 -> 编码 FastCGI 请求 -> 写入 -> 读取记录 -> 解析响应

sequenceDiagram
participant E as "PhpCgiExecutor"
participant C as "FastCgiCodec"
participant P as "php-cgi 进程"
E->>E : "选择后端 Socket"
E->>P : "连接 Unix Socket"
E->>C : "encode_request(method,path,req,env_overrides)"
C-->>E : "FastCGI 字节序列"
E->>P : "写入请求帧"
P-->>E : "stdout/stderr/end 帧"
E->>C : "decode_response(conn)"
C-->>E : "WorkerResponse"
E-->>E : "返回 HttpLogicDispatchOutcome"

图示来源 - src/executor/php_cgi_executor.v:42-82 - src/upstream/transport/fastcgi.v:79-249 - src/upstream/transport/fastcgi.v:266-317

章节来源 - src/executor/php_cgi_executor.v:1-118 - src/upstream/transport/fastcgi.v:1-386

VJSX 执行器（InProcVjsxExecutor）

职责
维护多个“车道”（线程级执行上下文），提供轮询选择、等待获取、释放能力
管理 Host 生命周期（模块加载、全局函数发现、事件绑定）
驱动 Lane 工作协程循环，处理 WebSocket 回调、快照、预热、亲和性任务
提供唤醒调度与优雅关闭
关键流程
选择车道 -> 获取可用车道 -> 投递任务 -> 等待结果 -> 释放车道

classDiagram
class InProcVjsxExecutor {
+kind() string
+model() LogicExecutorModel
+provider() string
+admin_details() LogicExecutorAdminDetails
+lane_count() int
+facade_snapshot() VjsxRuntimeFacade
+lane_snapshot() []VjsxExecutionLane
+ensure_lane_host(idx) !
+reset_lane_host(idx) void
+close() void
}
class VjsxExecutorState {
+lanes : []VjsxExecutionLane
+hosts : []VjsxLaneHost
+rr_index : int
+lane_wakeup_by_id : map[string]VjsxLaneWakeup
+session_store : MemoryStateStore
+signature_* : ...
}
class VjsxExecutionLane {
+id : string
+inflight : int
+healthy : bool
+dirty : bool
+last_error : string
}
class VjsxLaneHost {
+initialized : bool
+startup_completed : bool
+dirty : bool
+source_signature : string
+is_module_entry : bool
+temp_root : string
+session : RuntimeSession
+module_binding_ptr : *ScriptModule
}
InProcVjsxExecutor --> VjsxExecutorState : "持有状态"
VjsxExecutorState --> VjsxExecutionLane : "管理"
VjsxExecutorState --> VjsxLaneHost : "管理"

图示来源 - src/executor/inproc_vjsx_lifecycle.v:16-87 - src/executor/inproc_vjsx_lifecycle.v:102-118 - src/executor/inproc_vjsx_lifecycle.v:120-155 - src/executor/inproc_vjsx_lane_pool.v:5-30 - src/executor/inproc_vjsx_lane_pool.v:83-101 - src/executor/inproc_vjsx_lane_pool.v:126-144 - src/executor/inproc_vjsx_host_lifecycle.v:8-34 - src/executor/inproc_vjsx_host_lifecycle.v:175-192 - src/executor/inproc_vjsx_host_shutdown.v:23-72

章节来源 - src/executor/inproc_vjsx_lifecycle.v:1-155 - src/executor/inproc_vjsx_lane_pool.v:1-144 - src/executor/inproc_vjsx_host_lifecycle.v:1-193 - src/executor/inproc_vjsx_lane_worker_runtime.v:1-87 - src/executor/inproc_vjsx_lane_wakeup_runtime.v:1-58 - src/executor/inproc_vjsx_host_shutdown.v:1-73

依赖关系分析

PHP 执行器依赖
SocketWorkerExecutor 依赖 transport.WorkerFrameCodec/WorkerHttpRequestCodec 与 Unix Socket
PhpCgiExecutor 依赖 transport.FastCgiCodec 进行协议编解码
ManagedWorkerPool 负责子进程生命周期、优雅停止与重启退避
VJSX 执行器依赖
内部状态机与多通道任务队列（WebSocket、快照、预热、泵、亲和性）
运行时会话与模块加载、全局函数发现、事件绑定
唤醒调度与优雅关闭

graph LR
A["SocketWorkerExecutor"] --> B["WorkerFrameCodec"]
A --> C["WorkerHttpRequestCodec"]
D["PhpCgiExecutor"] --> E["FastCgiCodec"]
F["ManagedWorkerPool"] --> G["Unix Socket"]
H["InProcVjsxExecutor"] --> I["Lane Pool"]
H --> J["Lane Worker Runtime"]
H --> K["Host Lifecycle"]
H --> L["Shutdown"]

图示来源 - src/executor/socket_worker_executor.v:1-157 - src/executor/php_cgi_executor.v:1-118 - src/upstream/transport/worker_pool.v:1-219 - src/executor/inproc_vjsx_lifecycle.v:1-155 - src/executor/inproc_vjsx_lane_pool.v:1-144 - src/executor/inproc_vjsx_lane_worker_runtime.v:1-87 - src/executor/inproc_vjsx_host_lifecycle.v:1-193 - src/executor/inproc_vjsx_host_shutdown.v:1-73

章节来源 - src/upstream/transport/worker_pool.v:1-219 - src/upstream/transport/fastcgi.v:1-386