Problem with libzip with a lot off large files
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 95
- Forks
- 46
- PR merge metrics
- No merged PRs in 30d
Description
Hello,
in the default setting for a new backup job the zip module is used. It closes the zip file every 20 files and opens a new one and adds the next 20 files at the end. A temporary file is created as a copy of the original one and then the new data is added. The behavior is also libzip so wanted however with large files very much write load, partially over hours, is generated. In the operation of many wordpress websites, this is unfortunately not optimal. If you use e.g. tar for the backups, we do not notice the behavior. I suspect that many other users also find this behavior. Would it be possible to change the default setting to tar when creating new jobs?
greetings
Sam
Contributor guide
No contributing guide indexed for this repository
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
Start at inc/class-create-archive.php around line 386 and inspect how the default archive method is selected for new backup jobs. Confirm how tar and zip are represented in the job settings; done means newly created jobs use tar by default while existing choices remain unaffected.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php, wordpress
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100