cae6e4f60d0881d74b36ee141deb8f4bb9eeb787
The coordinator logs a line a minute: chunks fetched, articles/s, seconds a chunk, how busy its connections were. It showed the workstation's runs are bound by its 100 Mbit line now (10 connections 99% busy, ~89 Mbit/s: compressed XOVER is ~69 B an article on recent boneless), not by the code. The check that a compressed reply is complete (inflating it) ran on the coordinator's event loop, ~60 ms a chunk; now on a thread-pool thread. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Languages
TypeScript
95.5%
JavaScript
2.4%
CSS
1.4%
HTML
0.6%
Dockerfile
0.1%