mirror of
https://github.com/clash-verge-rev/clash-verge-rev.git
synced 2026-10-25 13:12:07 +08:00
Tunglies
b20fdc9b96
The cap of 8 was a conservative pick from 8ccb0b9a; that commit's own setup benchmark had the 4-worker / 8-blocking row as the best config: 639.3ms avg / 645.5ms max setup time and 22.1 avg threads, ahead of the adopted 8-worker row (650.1ms / 662.4ms, 26.0 threads). Startup parallelism is unaffected in practice: the setup join! polls cooperatively on one task, and CPU work (validation, script eval, YAML parse) runs on the spawn_blocking pool, which keeps its 8-thread cap through the existing 2x invariant. A 12h live session showed the 8 idle workers accumulating under 0.5s CPU total, so four parked stacks (~0.4MB dirty) are pure overhead.