Skip to content

Set Chromium MaxConnectionsPerProxy default to 16#183

Merged
sjmiller609 merged 1 commit intomainfrom
codex/set-maxconnectionsperproxy-default
Mar 19, 2026
Merged

Set Chromium MaxConnectionsPerProxy default to 16#183
sjmiller609 merged 1 commit intomainfrom
codex/set-maxconnectionsperproxy-default

Conversation

@sjmiller609
Copy link
Contributor

@sjmiller609 sjmiller609 commented Mar 18, 2026

Summary

Set Chromium’s default managed policy MaxConnectionsPerProxy to 16 in the kernel-images browser images.

Why

In live testing on a stealth Envoy VM with a 6-tab workload, Chromium’s default behavior allowed substantially higher upstream proxy fanout than desired. Setting MaxConnectionsPerProxy effectively clamps Chrome-to-proxy and proxy-to-origin connection counts much closer to the configured limit.

Observed results from the same workload:

  • Default: peak ~34 Chrome->Envoy connections, ~33 Envoy->Ping connections
  • MaxConnectionsPerProxy=16: peak ~17 / ~17
  • MaxConnectionsPerProxy=8: peak ~9 / ~9
  • MaxConnectionsPerProxy=4: peak ~7 / ~7

This makes 16 a good default for reducing proxy connection fanout without needing per-session configuration.

What changed

  • Added "MaxConnectionsPerProxy": 16 to the shared managed Chromium policy baked into the browser images.
  • Added assertions in existing e2e tests that read /etc/chromium/policies/managed/policy.json to verify the default is present.

Implementation details

The default policy is sourced from the shared image policy file and copied into the VM at /etc/chromium/policies/managed/policy.json, so this change applies to the browser image startup path directly.

Validation

  • Confirmed the managed policy JSON contains MaxConnectionsPerProxy: 16
  • Ran:
    • go test ./lib/policy
    • go test -run '^$' ./e2e

Note

Medium Risk
Changes a Chromium managed policy that can affect browser networking/concurrency behavior across all images. Added e2e checks reduce regression risk but policy changes may have wide runtime impact.

Overview
Updates the default managed Chromium policy to set MaxConnectionsPerProxy to 16 in shared/chromium-policies/managed/policy.json.

Hardens e2e coverage by asserting MaxConnectionsPerProxy exists and equals 16 in both the Chromium policy test and the enterprise extension policy test, so missing/changed policy values are caught early.

Written by Cursor Bugbot for commit 524dd6b. This will update automatically on new commits. Configure here.

Copy link
Contributor

@ulziibay-kernel ulziibay-kernel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@sjmiller609 sjmiller609 merged commit 582ab6f into main Mar 19, 2026
7 of 8 checks passed
@sjmiller609 sjmiller609 deleted the codex/set-maxconnectionsperproxy-default branch March 19, 2026 18:10
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.

2 participants