Had a look there: https://www.backblaze.com/cloud-storage/transaction-pricing
If each small file results in 1 chunk and each chunk is stored into a separate cloud object, that would mean 1M small (new) files cost $4 to back up using b2.
Also bad: they are also accounting per "ls" (listing 1 directory) and as current borg2 beta11 uses a nested directory structure of 1+256+65536 directories, just doing one full list to get all object IDs are already more than 64k "ls" calls (borg check and borg compact do that).
So, backblaze b2 is accounting "per file / per key / per object" and "per ls" - and not just per MB/GB/TB storage or traffic.
Is that common, do other providers do that also?
Had a look there: https://www.backblaze.com/cloud-storage/transaction-pricing
If each small file results in 1 chunk and each chunk is stored into a separate cloud object, that would mean 1M small (new) files cost $4 to back up using b2.
Also bad: they are also accounting per "ls" (listing 1 directory) and as current borg2 beta11 uses a nested directory structure of 1+256+65536 directories, just doing one full list to get all object IDs are already more than 64k "ls" calls (borg check and borg compact do that).
So, backblaze b2 is accounting "per file / per key / per object" and "per ls" - and not just per MB/GB/TB storage or traffic.
Is that common, do other providers do that also?