Skip to content

Conversation

@CharlieR-o-o-t
Copy link

Related to issue: #3081

"slab_reclaimable" should be excluded from container_memory_working_set_bytes.

"slab_reclaimable" is only unused cached kernel structured, which can be freed on mem pressure.

@google-cla
Copy link

google-cla bot commented Jan 5, 2025

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

@asbachb
Copy link

asbachb commented Apr 2, 2025

@cwangVT do you have any opinion on that change?

@fabiand
Copy link

fabiand commented Jul 3, 2025

@dims it would be great if you could give this PR a look )I think there have been similar ones in the past).

For context see #3081 (comment) , similar #3286

tldr; today, workingset contains reclaimable memory, which then in turn is leading to incorrect decisions.

@CharlieR-o-o-t
Copy link
Author

Guys, PR 7 months old. Is anybody able to take a look?

@github-actions
Copy link

github-actions bot commented Dec 9, 2025

This PR is stale because it has been open 90 days with no activity. This PR will be closed in 30 days unless new comments are made or the stale label is removed. To skip these checks, apply the "lifecycle/frozen" label.

@github-actions github-actions bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 9, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants