Hello Nikolaus,
currently S3QL uses a fixed buffer size of 64KB. With that buffer size I
can get upload speeds of 100 MBit/s. Not that bad. But when I increase
that constant from 64KB to e.g. 4MB the same setup can saturate a
1GBit/s network connection.
Do you have any reservations against making BUFSIZE configurable with an
extra argument to most of the command line tools so that – if one
chooses – can tailor the BUFSIZE to the system/use case.
I just wanted to ask in advance before going thru the hassle of creating
a pull request.
--
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].
To view this discussion on the web visit
https://groups.google.com/d/msgid/s3ql/070fe045-026a-fb63-3c5d-6d874cd6f3b2%40jagszent.de.
For more options, visit https://groups.google.com/d/optout.
