Bryce
4882c1c9cf
dirty-sales-summaries index-pulled from [client-id true] and then filtered by client. index-pull returns a lazy seq running to the END of the index, and a lazy filter does not stop it, so for every client the job walked every summary belonging to every client sorting after it — pulling their items along the way. Quadratic in the number of summaries. take-while stops at the client boundary instead, which is safe because :sales-summary/client+dirty sorts by client first, so a client's dirty summaries are contiguous from that start point. Measured on a 14,458-summary database: 1,321ms -> 5.6ms per client, a 237x improvement, with identical results. A full refresh had been degrading from ~180 client-days a minute to ~3 as summaries accumulated. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>