envoyproxy/gateway

Scaling down routes not scaling down memory usage

Open

#4,498 opened on Oct 23, 2024

View on GitHub
 (2 comments) (0 reactions) (0 assignees)Go (802 forks)auto 404
help wanted

Repository metrics

Stars
 (2,871 stars)
PR merge metrics
 (PR metrics pending)

Description

Metrics

Test Name Envoy Gateway Memory (MiB) Envoy Gateway CPU (s) Envoy Proxy Memory (Avg) (MiB) Envoy Proxy CPU (Avg) (s)
scale-up-httproutes-10 107.11 0.74 25.85 30.44
scale-up-httproutes-50 136.46 1.42 31.97 60.84
scale-up-httproutes-100 136.98 2.75 38.13 91.64
scale-up-httproutes-300 141.98 14.64 60.31 124.75
scale-up-httproutes-500 157.41 26.76 80.52 158.63
scale-up-httproutes-1000 179.77 57.89 130.77 197.64
scale-down-httproutes-500 164.67 85.83 130.91 233.84
scale-down-httproutes-300 152.14 96.66 131.07 266.26
scale-down-httproutes-100 146.73 106.85 127.11 298.33
scale-down-httproutes-50 161.01 107.92 127.04 329.02
scale-down-httproutes-10 202.45 108.52 126.36 359.48

Originally posted by @arkodg in https://github.com/envoyproxy/gateway/issues/4287#issuecomment-2430569347

Contributor guide

Research direction
Investigate memory management in Envoy Gateway during scale down of HTTP routes. Look at how route configurations are cleaned up and why memory is not released.
Tech stack
go
Domain
backendinfrastructure
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Go
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
30