Uploaded chunks with size smaller than -min-chunk-size?

I have a storage configured with fixed chunk size of 1 MB:

INFO CONFIG_INFO Average chunk size: 1048576
INFO CONFIG_INFO Maximum chunk size: 1048576
INFO CONFIG_INFO Minimum chunk size: 1048576

When I run backup, I have, as expected:

...
INFO UPLOAD_PROGRESS Uploaded chunk 3462 size 1048576, 20.75MB/s 00:05:05 12.6%
INFO UPLOAD_PROGRESS Uploaded chunk 3463 size 1048576, 20.78MB/s 00:05:05 12.6%
INFO UPLOAD_PROGRESS Uploaded chunk 3464 size 1048576, 20.80MB/s 00:05:04 12.6%
...

But I also have:

...
INFO UPLOAD_PROGRESS Uploaded chunk 2164 size 2222, 17.24MB/s 00:06:35 5.9%
INFO UPLOAD_PROGRESS Uploaded chunk 2163 size 3086, 17.24MB/s 00:06:35 5.9%
INFO UPLOAD_PROGRESS Uploaded chunk 2165 size 3022, 17.24MB/s 00:06:35 5.9%
INFO UPLOAD_PROGRESS Uploaded chunk 2166 size 1374, 17.24MB/s 00:06:35 5.9%
...

The repository does have a lot of small files, but even so all chunks should have the size of 1 Mb, right?

I have the same on a Vertical Backup storage but I believe it’s perfectly normal. Files are chunked, those chunks are then compressed and encrypted. Presumably some of those chunks end up being very well compressed!

No, that is not because of compression. Those sizes are the sizes of chunks before compression.

Some of them are less than 1M because if the storage is configured to contain fixed-size chunks, Duplicacy doesn’t pack small files. Each file smaller than 1M will be uploaded as a single chunk.

2 Likes

I thought it was the size of the chunks themselves, since most of the chunks’ files in storage have exactly 1 M. :thinking: