On Jul 02 2016, Peter Auyeung <[email protected]> wrote:
>>> I am trying to reduce the cloud put get traffic during incremental
>>
>> Then you should be working with two mounted S3QL file systems (one
>> using the local backend and one using the Google Storage backend) and do
>> the synchronization using e.g. rsync.
>
> I was using rsync. As I asked in a different thread. Due to the amount
> of small files in s3ql. The rsync generated lots of put get traffic
> during incremental.
There's no way to avoid that. At the moment, S3QL uses at least one
object per stored file. As a workaround, you can store zip/tar the files
before putting them on the S3QL file system.
But again, this is the case no matter what backend you use and no matter
how you synchronize. I'm still at a loss what your actual
question/problem/intention is.
Best,
-Nikolaus
--
GPG encrypted emails preferred. Key id: 0xD113FCAC3C4E599F
Fingerprint: ED31 791B 2C5C 1613 AF38 8B8A D113 FCAC 3C4E 599F
»Time flies like an arrow, fruit flies like a Banana.«
--
You received this message because you are subscribed to the Google Groups
"s3ql" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
