Skip to content

Use a real network MTU when throttling localhost - #115

Merged
soulgalore merged 1 commit into
mainfrom
localhost-mtu-1500
Oct 13, 2026
Merged

soulgalore merged 1 commit into
mainfrom
localhost-mtu-1500

Conversation

@soulgalore

Copy link
Copy Markdown
Member

Loopback uses 65536-byte packets, so the server can send a whole page in one go and the browser's receive window becomes the limit. How fast that window opens depends on when the browser reads the data, so WebPageReplay runs fell into groups that were a whole round trip apart (FCP spread 300 ms for the same recording).

With 1500-byte packets, the transfer grows like on a real network and the runs are steady (FCP spread 36 ms on the same page). Stop restores the loopback default.

Assisted-by: Claude Opus 5.5 noreply@anthropic.com

Loopback uses 65536-byte packets, so the server can send a whole page in one go and the browser's receive window becomes the limit. How fast that window
opens depends on when the browser reads the data, so WebPageReplay runs fell into groups that were a whole round trip apart (FCP spread 300 ms for the
same recording).

With 1500-byte packets, the transfer grows like on a real network and the runs are steady (FCP spread 36 ms on the same page). Stop restores the loopback
default.

Assisted-by: Claude Opus 5.5 noreply@anthropic.com
@soulgalore
soulgalore merged commit 3922f3c into main Oct 13, 2026
6 checks passed
@soulgalore
soulgalore deleted the localhost-mtu-1500 branch October 13, 2026 06:33
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