You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As part of recent profiling comparison with nginx:
Right now how Envoy handles headers is extremely inefficient. We use a list, along with std::string, and generally iterate over the entire list for remove operations, etc.
Move to a more efficient implementation that:
Looks at each header on receive and store direct pointer into the list if Envoy will ever use it (via hash lookup). All add/remove/modify operations become O(1).
Move away from std::string, implement explicit short string optimization, with sentinel for common headers.
The text was updated successfully, but these errors were encountered:
…nvoyproxy#120)
Description: use http_parser in http inspector
Risk Level: Med
Testing: Unit test
Docs Changes: N/A
Release Notes: N/A
Signed-off-by: crazyxy <yxyan@google.com>
Signed-off-by: Piotr Sikora <piotrsikora@google.com>
As part of recent profiling comparison with nginx:
Right now how Envoy handles headers is extremely inefficient. We use a list, along with std::string, and generally iterate over the entire list for remove operations, etc.
Move to a more efficient implementation that:
The text was updated successfully, but these errors were encountered: