Right. So the answer to that is: It can, and does, but it is missing
the obvious optimization of skipping the network stack for
local-disk-to-local-disk transfer.
It might still be fast (enough); you'd have to benchmark it to see.
See below for demonstration.
Its pretty convenient to try local-t
I read G's question as whether jcp can efficiently update incremental
backups from primary to secondary local storage, e.g. daily backup of a
home dir to an attached memory stick or an alternate folder on the same
filesystem.
On Friday, March 28, 2025 at 3:55:30 PM UTC-7 Jason E. Aten wrote:
>
Yes? The question is a bit confusing. jcp copies from
host1 filesystem -> over the network -> (jsrv running on) host2 filesystem,
and while (for testing mostly) you can leave off the host: prefix on
both giver and taker, to copy things from local disk
over the TCP/UDP network stack, and back to
is it able to use a local storage as backup?
Thanks
On Thursday, March 20, 2025 at 10:04:45 PM UTC-7 Jason E. Aten wrote:
> I've open sourced jcp, my rsync-like file transfer library and CLI.
>
> By using Go's fabulous multicore support, jcp can do diff-only filesystem
> syncs
> up to 3x faster
