backup packing time
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 272
- Forks
- 37
- PR merge metrics
- No merged PRs in 30d
Description
Hello everyone,
I am currently having the following problem with the backup app.
I started a full backup a week ago. During this time, the packing was also carried out quickly and without any problems. From the point where the health check was set to „completed“, the packing only works extremely slowly. My backup is around 700GB. The packing includes the points that any zip files are packed in 100MB files. Around 2000 files were packed before the health check. Since then, after 7 days, only about 100 files are changed into 100MB files. It seems to me that the packing process keeps getting interrupted, which I can see from the CPU usage. The packing is always active for about 15-20 minutes. This state is then interrupted and only started again after approx. 65 minutes.
My Nextcloud runs on Docker. I hope you can help me with this problem.
greeting
Stefan
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named. Start by tracing the backup packing flow around the health-check completion state in the Docker deployment, then reproduce the slowdown with a large backup and determine what is interrupting packing; done means packing proceeds consistently after the health check.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, php
- Domain
- backend, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100