Skip to content

Load request payloads lazily - #66

Open
ipo wants to merge 1 commit into
snipeship:mainfrom
ipo:pr/lazy-request-payloads-upstream
Open

Load request payloads lazily#66
ipo wants to merge 1 commit into
snipeship:mainfrom
ipo:pr/lazy-request-payloads-upstream

Conversation

@ipo

@ipo ipo commented Aug 1, 2026

Copy link
Copy Markdown

The /requests page was a real performance hog, constantly eager-reloading 200 requests at a time, which caused significant strain over time. I had 5.6-sol rewrite it to be lazy-loading instead, it should be a minimal-impact improvement if you merge it.

Performance Numbers

The /requests page refreshes every 10 seconds and displays up to 200 rows. Previously, each refresh loaded all stored request and response bodies, although the table only needs metadata.

For 0.8 MiB payloads (my average), this could transfer 152 MiB of unnecessary data per refresh—15 MiB/s or 53 GiB/hour while the page remained open. The new implementation loads only metadata and fetches a payload when the user opens or copies that request. It also removes redundant full-payload transfers between the worker, server, and connected dashboards.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant