Skip to content

Use / expose resource control capabilities from systemd to ensure Restic stays within safe limits #668

Description

@frittentheke

Knowingly Restic can be memory hungry with vastly changing requirements over time. Resticprofile checks for a minimal amount of RAM before Restic is invoked: https://creativeprojects.github.io/resticprofile/usage/memory/index.html

To further ensure Restic does not push the system OOM it might be sensible to also leverage the resource control capabilities of systemd (https://www.freedesktop.org/software/systemd/man/latest/systemd.resource-control.html) like MemoryMax.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions