envoyproxy/envoy

Memory utilization can grow significantly when struct fields are used for configuration of Envoy components

Open

#5 965 ouverte le 15 févr. 2019

Voir sur GitHub
 (2 commentaires) (0 réactions) (0 assignés)C++ (5 373 forks)batch import
help wantedtech debt

Métriques du dépôt

Stars
 (27 997 stars)
Métriques de merge PR
 (Merge moyen 8j) (378 PRs mergées en 30 j)

Description

Title: Memory utilization can grow significantly when struct fields are used for configuration of Envoy components.

Description: In my test bootstrap config with http_connection_manager configuration in "config" field with 50K virtual hosts uses ~1807MB. The same configuration, but put in "typed_config" results in 292MB. This is due to maps being created to represent struct fields during reflection in MessageUtil::checkForDeprecation call.

[optional Relevant Links:] Test that uses "typed_config" for http_connection_manager configuration: https://github.com/dmitri-d/envoy/blob/b6b2a9cff293a1bd97166e742091900fa36ce388/test/integration/rds_memory_stats_test.cc Similar to the test above, but uses "config", which is a struct field: https://github.com/dmitri-d/envoy/blob/rds-memory-stats/test/integration/rds_memory_stats_test.cc

Guide contributeur