Issue #7192
closedEnable systemd resource tracking for Pulp units
Description
Problem 1: Checking memory consumption of tasks running on workers is a multi-step process (hunt down PID, disambiguate it from all the others, etc).
Problem 2: It's difficult to measure the memory consumption total across multiple tasks and multiple workers.
Systemd allows you to opt-in to memory tracking, and it tracks across forks as well. So the memory consumption of a worker unit is the consumption of the entire group of processes.
Likewise the memory consumption of the "slice" is the memory consumption of the group of worker units, which is neat.
Added by dalley over 4 years ago
Added by dalley over 4 years ago
Revision 91fda4e7 | View on GitHub
Ask systemd to track memory consumption
Allows tracking memory consumption on a per-unit and per-cgroup basis.
https://www.freedesktop.org/software/systemd/man/systemd.resource-control.html#MemoryAccounting=
Updated by dalley over 4 years ago
- Category set to Installer - Moved to GitHub issues
Updated by dalley over 4 years ago
- Status changed from ASSIGNED to MODIFIED
Applied in changeset ansible-pulp|91fda4e7a6a7587a6614c67e6a9a274e70f85c57.
Updated by ttereshc about 4 years ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
- Sprint/Milestone deleted (
3.8.0)
Ask systemd to track memory consumption
Allows tracking memory consumption on a per-unit and per-cgroup basis.
https://www.freedesktop.org/software/systemd/man/systemd.resource-control.html#MemoryAccounting=
closes: #7192 https://pulp.plan.io/issues/7192