[Borgbackup] CPU/time use of Borg

[Dmitry Astapov]

This is how a typical backup looks for me :

Duration: 1 minutes 41.41 seconds
Number of files: 558471
------------------------------------------------------------
------------------
                       Original size      Compressed size    Deduplicated
size
This archive:               78.84 GB             50.79 GB             31.52
MB
All archives:               23.03 TB             14.64 TB            101.51
GB

                       Unique chunks         Total chunks
Chunk index:                  778813            170023300

This is over wifi to a NAS server on the local network.

Backups are taken every 30 minutes, process on the source system uses about
330 Mb VSS / 230 Mb RSS.

There must be something in your setup that causes slowness (source
filesystem? Target filesystem? No stable inodes ? No stable mtimes? ....).

On Tue, May 5, 2020, 22:33 MRob <mrobti at insiberia.net> wrote:

> >> Another question: after for example a year of backup does it require
> >> alot more CPU/RAM to compute chunk deltas?
> >
> > cpu/time will generally be proportional to the number of chunks you
> > have in
> > total (it may vary from operation to operation)
>
> My simple test over local network took alittle over 2min/Gb on 1st
> backup. Its ok if only 1st time. But 2nd time was still over 1min/Gb and
> 3rd backup very close to 2min/Gb again. (its for busy production server)
>
> I like borg, but if it wont ever get faster maybe I can't use borg :(
> Is borg only for fast & non-busy hardware?
>
> (see other thread, asking way for offload operations from client to
> backup server)
> _______________________________________________
> 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/20200505/d56f5041/attachment.html>