Skip to content

Avoid excessive hashing for well-known header lookups - #46560

Draft
etruong42 wants to merge 1 commit into
envoyproxy:mainfrom
etruong42:headerregistry
Draft

Avoid excessive hashing for well-known header lookups#46560
etruong42 wants to merge 1 commit into
envoyproxy:mainfrom
etruong42:headerregistry

Conversation

@etruong42

Copy link
Copy Markdown
Contributor

Commit Message:
Additional Description:
Risk Level:
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Fixes commit #PR or SHA]
[Optional Deprecated:]
[Optional API Considerations:]

@repokitteh-read-only

Copy link
Copy Markdown

As a reminder, PRs marked as draft will not be automatically assigned reviewers,
or be handled by maintainer-oncall triage.

Please mark your PR as ready when you want it to be reviewed!

🐱

Caused by: #46560 was opened by etruong42.

see: more, trace.

@etruong42
etruong42 force-pushed the headerregistry branch 12 times, most recently from df2e0e8 to 146e313 Compare August 13, 2026 02:03
Also lazily allocate the `data_storage_` map.

Change-Id: I8231d1d58642338f5401083275f6e6a9fe864ac8
Signed-off-by: Ethan Truong <ethantruong@google.com>
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