Backups index load time

bluelinq-computers

Is there any work planned to speed up the Backups index page?

For those of us running both an S3 destination and a server with the backup role, this page takes a couple of genuine minutes to load. It's just a spinner the whole time. It does eventually load and then render, so nothing is broken, but the wait is long enough to be annoying.

Adam

S3 can be very slow because it relies on multiple API calls to a 3rd party environment where we don't control the performance or the latency.

We might be able to add a caching layer of some kind. However my recommendation would be to ensure your Enhance backup server is totally independent of the provider where you host your live websites then disable the S3 backups.

bluelinq-computers

Adam I know you and I've discussed this in the past and I know there is definitely some latency you do not control.

That said, I'd really encourage the team to look at a caching layer here, especially for S3. Once a backup has been written, its metadata is immutable. The only thing that actually changes between page loads is the newest snapshot at the head of the list.

Ideally we'd persist the snapshot index locally and render from that immediately. Refresh it when a backup job completes, on a TTL, or via an explicit "Refresh" button so the operator can force a re-read when they need ground truth.