TW

NVME SSD in my workstation (with few big VM files) ``` workers files dirs bytes time (seconds) bandwidth (per second) 1 29 14 60873793654 22.810396927 2668686294 # 2.67GB/s 2 29...

Same, but with more and smaller/medium files. ``` workers files dirs bytes time (seconds) bandwidth (per second) 1 268881 35541 59742969794 40.711983296 1467454173 # 1.47 GB/s 2 268881 35541 59742969794...

@fschulze borg does not open unchanged files. but it fetches stats, xattrs, acls, bsdflags.

@jkahrs how many disks in total?

For the case of a **changed** file, there is also an additional `fstat(fd)` call **after** reading the file's content, to check whether the file changed while we read it.

@FabioPedretti Thanks for doing measurements. Nice to see that in some cases it got faster. For the case (usage with `--nobsdflags`), where it got slower: - for 1.1, nobsdflags on...

it only straced the main process (and there is nothing interesting in there). you need to use `strace -f ...` so it also follows to child processes.

that's because 1.1.x works filename-based (giving each call the path/filename) and 1.2 works fd-based (stats/opens once with the name, then uses the fd).

tar: doesn't do much here: - I only see it `stat`-ing the files. - It doesn't open the file (likely due to 0 bytes). - It does not try to...

borg 1.2: ``` # name-based stat relative to dir fd to determine file type for dispatching to correct handler newfstatat(6, "testfile-2", {st_mode=S_IFREG|0644, st_size=0, ...}, AT_SYMLINK_NOFOLLOW) = 0 # name-based open...