New sync method in v1.36 and Backblaze B2 Class C Transaction Cap

I’d echo the impact to deprecating the old sync method. I have about 350GB that I am looking at syncing via CRON. I don’t have a lot that changes, but it still has to index and check. I just ran into the issue when I upgraded rclone and blew my safety cap at 15k transactions two days in a row.

I agree that sucking up 4gb of memory is painful, but is there some way we can do a middle ground? Or another API we can use?

For my use there is only one read/write source so technically for my case it could be cached maybe…

I do agree two algorithms is twice as hard, though.

1 Like