envoyproxy/envoy

Why overload manager can't work if envoy build with out Tcmalloc and using jemalloc

Open

#38,468 opened on Feb 16, 2025

View on GitHub
 (2 comments) (0 reactions) (0 assignees)C++ (5,373 forks)batch import
area/overload_managerenhancementhelp wanted

Repository metrics

Stars
 (27,997 stars)
PR merge metrics
 (Avg merge 8d) (378 merged PRs in 30d)

Description

Description:

If config overload manager with envoy.resource_monitors.fixed_heap as resource monitor and with tcmalloc= disable This overload manager seems not work. So if we are using jemalloc , this Envoy overload manager seems not work ? So why ? and how to fix this problem if we still need use jemalloc and we also want the overload manager work.

resource_monitors:

  • name: "envoy.resource_monitors.fixed_heap"

Contributor guide

Research direction
Investigate the overload manager's interaction with memory allocators. Check the code for fixed heap resource monitor to understand how it uses tcmalloc specific features. If using jemalloc, identify compatibility issues and propose a solution.
Tech stack
cpp
Domain
backend
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.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
C++Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40