[Borgbackup] Storage, CPU, RAM comparisons

[Panayotis Katsaloulis]

Just stating my own experience.
In a real-file source-code related of 6GB (all my code I ever written with their datafiles) Borg backup was the one with the best storage handling and at the same time the ability to directly mount your repository and look back in history.
There’s no other tool that can do this best than borgbackup.


--
Panayotis
On 4 May 2020, 12:22 AM +0300, MRob <mrobti at insiberia.net>, wrote:
> Hello,
> I reading about borg and looking exciting to me. Thank you for a great
> software!
>
> Can I ask, I have only seen one storage and CPU comparison:
> https://github.com/gilbertchen/benchmarking
>
> With deduplication, why is disk usage so much higher than duplicity? Can
> I assume disk usage of duplicity would be similar to rdiff-backup?
> Because rdiff/duplicity stores deltas of each file but deduplication
> strategy stores common file blocks I expect borg to being far smaller
> storage needs. Why is that wrong?
>
> Also like to ask what CPU, RAM usage of borg. I read only one place CPU
> use if very high for borg compare to rsync.
> Thank you!
> _______________________________________________
> Borgbackup mailing list
> Borgbackup at python.org
> https://mail.python.org/mailman/listinfo/borgbackup
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/borgbackup/attachments/20200504/36c07c3f/attachment.html>