Gregory SchierandClaude Opus 5.5 1a994f7532 Keep the proxy app fast with many flows ...

The app held every flow in memory and redid all of its work for each new
one: the sidebar mounted every domain and path node (its tree scrolled
inside a container that never bounded it), every tree row looked up its
atoms by scanning every atom the family had made, and the layout, detail
pane and list rows re-rendered per flow. At 3,000 flows each new one cost
about 90 ms of main thread, more than the traffic left time for.

The app now holds a window of the newest 2,000 flows, applies new ones in
batches, and loads older ones in pages from the database on scrolling to
the top, through a new list_flows RPC that pages in SQL. The database
keeps every flow.

Also adds clear_flows: an RPC, POST /flows/clear on the control API, and
a Clear button in the header that Cmd+K opens, confirming first.

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

2026-10-28 09:52:00 -07:00

..

fixtures

PR 2: proxy services (#787)

2026-10-27 15:19:50 -07:00

control.rs

Keep the proxy app fast with many flows

2026-10-28 09:52:00 -07:00

flow.rs

PR 2: proxy services (#787)

2026-10-27 15:19:50 -07:00