Heavy routes run in worker processes, one per heavy slot (issue #133, BUG-1493)

The single ThreadingHTTPServer ran pure-Python v5 score / block_scan / report
reference under one GIL, so the gate's two slots shared a core. start_server
now starts a spawn pool (workers = heavy concurrency, PYTHONHASHSEED=0, engine
pre-imported); those three routes call the same compute method in a worker.
Over HTTP: score alone 4.74 s, two at once 5.01 / 4.58 s (1.06x; in-process
1.56x). Results equal except per-process fingerprints; report markdown equal.
~165 MB extra. A crashed pool answers inline and restarts; off with
JYOTISH_HEAVY_COMPUTE_PROCESSES=0; tests calling compute methods unchanged.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

This commit is contained in:

Jesse_Chen

2026-10-28 14:28:05 +08:00

co-authored by

Claude Opus 5.5

parent 5fd79a5649

commit 8d1cb4a53b

6 changed files with 266 additions and 8 deletions

									
										scripts/api_process_pool/__init__.py
									
		+1
		
												View File
												
				@@ -0,0 +1 @@

				"""Process pool for the heaviest API computations (issue #133)."""

				`@@ -0,0 +1 @@`
				`"""Process pool for the heaviest API computations (issue #133)."""`