mirrors/git-annex
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Added a comment: Rsync vs S3

Browse source
This commit is contained in:
emi@f69ad15b49bfecb4ea3836b6480e5ab8df9a5f7d 2023-10-15 15:01:24 +00:00 committed by admin
parent 892d87efa4
commit a73f77bcc8
1 changed files with 9 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

9
doc/tips/using_Backblaze_B2/comment_1_705156f867db0a6e4951e5c6774b128a._comment Normal file
View file

@ -0,0 +1,9 @@
[[!comment format=mdwn
username="emi@f69ad15b49bfecb4ea3836b6480e5ab8df9a5f7d"
nickname="emi"
avatar="http://cdn.libravatar.org/avatar/84bf8bb9fcad258f264f28740d91981e"
subject="Rsync vs S3"
date="2023-10-15T15:01:24Z"
content="""
I've been using the Rsync B2 special remote for a while now, and it seems to produce a very large number of Class C (the most expensive class) transactions while performing certain operations (uploads & dropunused, at least). I just started using the S3 special remote today, and while I've only uploaded so far, it seems to produce much fewer Class C transactions (after uploading a pretty large number of files, I'm only seeing 13). If cost is a concern, that might be one reason to prefer the S3 special remote. That said, this is mostly anecdotal. Perhaps someone else might chip in empirical data or check out the code to back up these observations.
"""]]