fix(postgres): chat history slows under concurrent reads (#190129) - PostgreSQL history workers spend most of a request blocked on bridge replies, so the shared two-worker reader cap queued concurrent chat.history requests while CPU sat idle. - History on PostgreSQL agent stores now uses two workers per CPU above one, capped at four. SQLite and unset engines keep the reader size. - The history pool resolves its size on first use, because boot installs the database engine after the lane module is imported. - Transcript search and the other transcript lanes are unchanged. - Tests: per-engine sizing table, and a lane test that installs the engine after import (PostgreSQL 4, SQLite 2). - Docs: runtime architecture sizing note and the PostgreSQL backend budget.
fix(postgres): chat history slows under concurrent reads (#190129)
Find Your Interest
- Accelerate Molecular Dynamics Simulations with Accurate, Flexible Primitives Using NVIDIA cuPotential
- Rumor: iPhone 20 Pro Could Get a New Main Camera Sensor
- DJI Mini 5 Pro Packs a 1-Inch Sensor Without the Bulk
- ★ The Dalrymple Report: AI, Meta and iPhone 18 Pro Max
- Xiaomi’s 18 Pro Series Phones are Now Available Globally
- The BMW M4 Convertible Could Go Electric. Everything We Know About The ZA3
- A Stranger Knows Your Bank Balance and Offers to Help — Here’s the Scam Behind It
- Xiaomi 18 Pro hands-on: Undeniably cool, incredibly powerful
- The $50 Per Hour Search Engine
- Fridge Controller Attacks: Researchers Find Six Zero-Days in an Hour





