Been looking into resource constraining Kopia through systemd to prevent the Go binary from eating through too many resources. Anyone running a system like this?
Been looking into resource constraining Kopia through systemd to prevent the Go binary from eating through too many resources. Anyone running a system like this?
In general, if you want to decrease CPU and memory usage, the first and foremost thing you should do is decrease parallelism via the kopia settings (i. e. either as a global policy for scheduled backups, or directly as parameter when creating a snapshot). No idea about kopia-ui, but the settings are probably exposed there? Not a ui user.
You can also decrease resource usage by tweaking compression settings, or disabling compression completely.
Once that is done, you can experiment with hard limits. I’m not sure how resilient kopia is in the presence of those, or how performance might suffer - all I can say is I backed up 2TB of data just 3 or 4 days ago using reasonable settings, and it did not tax the host overly much.
What sort of system specs are you working with?