Abysmal performance during backup restore

[dominikandreas]

Describe the issue you are experiencing

Restoring backups even on a yellow with cm5, 8gb Ram and 1TB NVME does not reach more than a few MB/s (averaging ~4MB/s according iotop) with CPU constantly at 100%.

This is far from optimal, in theory speeds in excess of 200MB/s should be possible even with compression (e.g. using zstd instead of gzip), but even with gzip I'd expect at least an order of magnitude more than what I get.

I'm not sure what exactly causes this, but wanted to open this issue as a starting point to investigate improvements. My hunch is that tar with gzip in python space is suboptimal, but not sure. Any pointers appreciated.

Maybe a short term "fix" could also adding an option to disable compression (in my case it's not really needed, I would much rather be able to restore my backups in less than a day or two).

What type of installation are you running?

Home Assistant OS

Which operating system are you running on?

Home Assistant Operating System

Steps to reproduce the issue

...

Anything in the Supervisor logs that might be useful for us?

Nothing relevant to add here.

System information

System Information

version	core-2025.3.0.dev0
installation_type	Home Assistant OS
dev	true
hassio	true
docker	true
user	root
virtualenv	false
python_version	3.13.1
os_name	Linux
os_version	6.6.62-haos-raspi
arch	aarch64
timezone	Europe/Berlin
config_dir	/config

Home Assistant Community Store

GitHub API	ok
GitHub Content	ok
GitHub Web	ok
HACS Data	ok
GitHub API Calls Remaining	5000
Installed Version	2.0.4
Stage	running
Available Repositories	1563
Downloaded Repositories	21

Home Assistant Cloud

logged_in	false
can_reach_cert_server	ok
can_reach_cloud_auth	ok
can_reach_cloud	ok

Home Assistant Supervisor

host_os	Home Assistant OS 14.2
update_channel	stable
supervisor_version	supervisor-2025.02.4
agent_version	1.6.0
docker_version	27.2.0
disk_total	916.2 GB
disk_used	49.0 GB
healthy	true
supported	failed to load: Unsupported
host_connectivity	true
supervisor_connectivity	true
ntp_synchronized	true
virtualization
board	yellow
supervisor_api	ok
version_api	ok
installed_addons	Advanced SSH & Web Terminal - Debian base (2024.12.16), Mosquitto broker (6.5.0), TimescaleDB (4.2.0), MQTT Explorer (browser-1.0.1), Portainer (2.27.0), RaspberryMatic CCU (3.79.6.20250220), Increase Swap (1.1.3), Grafana (10.4.2), WireGuard (0.11.0)

Dashboards

dashboards	3
resources	15
views	18
mode	storage

Network Configuration

adapters	lo (disabled), end0 (enabled, default, auto), hassio (disabled), docker0 (disabled), veth316f9ff (disabled), vethe8c6309 (disabled), veth6c5202f (disabled), vethfe50d8c (disabled), veth370eb9f (disabled), veth40fbeeb (disabled), veth230c64c (disabled), vetha520292 (disabled), veth58d546d (disabled), vethd987c55 (disabled), veth18bca5e (disabled), veth9f02e06 (disabled)
ipv4_addresses	lo (127.0.0.1/8), end0 (192.168.1.217/24), hassio (172.30.32.1/23), docker0 (172.30.232.1/23), veth316f9ff (), vethe8c6309 (), veth6c5202f (), vethfe50d8c (), veth370eb9f (), veth40fbeeb (), veth230c64c (), vetha520292 (), veth58d546d (), vethd987c55 (), veth18bca5e (), veth9f02e06 ()
ipv6_addresses	lo (::1/128), end0 (fe80::4fc2:a546:9ce1:2fcc/64), hassio (fe80::42:dff:fed0:65a/64), docker0 (fe80::42:9fff:fe6d:209b/64), veth316f9ff (fe80::5043:b4ff:fee2:69c/64), vethe8c6309 (fe80::943f:88ff:fe02:7bfa/64), veth6c5202f (fe80::98f9:c8ff:fec6:b760/64), vethfe50d8c (fe80::28c6:eff:fead:bf75/64), veth370eb9f (fe80::d000:99ff:fe72:8f1d/64), veth40fbeeb (fe80::98c7:14ff:fee1:da55/64), veth230c64c (fe80::5060:aeff:fe8c:3315/64), vetha520292 (fe80::b8ac:1dff:fef8:f9d7/64), veth58d546d (fe80::8dc:c5ff:fe3e:2d1d/64), vethd987c55 (fe80::8c3:8aff:fecf:78df/64), veth18bca5e (fe80::4c8e:7bff:fefb:575e/64), veth9f02e06 (fe80::7c8b:bcff:feb5:9891/64)
announce_addresses	192.168.1.217, fe80::4fc2:a546:9ce1:2fcc

Supervisor diagnostics

No response

Additional information

No response

[github-actions]

There hasn't been any activity on this issue recently. Due to the high number of incoming GitHub notifications, we have to clean some of the old issues, as many of them have already been resolved with the latest updates.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by adding a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thank you for your contributions.