diff options
Diffstat (limited to 'doc/bugs/S3_memory_leaks/comment_3_5e9cecb0e2ec7602963406779b6e3c1f._comment')
| -rw-r--r-- | doc/bugs/S3_memory_leaks/comment_3_5e9cecb0e2ec7602963406779b6e3c1f._comment | 12 |
1 files changed, 12 insertions, 0 deletions
diff --git a/doc/bugs/S3_memory_leaks/comment_3_5e9cecb0e2ec7602963406779b6e3c1f._comment b/doc/bugs/S3_memory_leaks/comment_3_5e9cecb0e2ec7602963406779b6e3c1f._comment new file mode 100644 index 000000000..a7bb0265f --- /dev/null +++ b/doc/bugs/S3_memory_leaks/comment_3_5e9cecb0e2ec7602963406779b6e3c1f._comment @@ -0,0 +1,12 @@ +[[!comment format=mdwn + username="http://joeyh.name/" + ip="209.250.56.112" + subject="comment 3" + date="2014-08-02T23:08:44Z" + content=""" +hS3's author seems to have abandoned it and it has other problems. I should try to switch to a different S3 library. + +There is now a workaround; S3 special remotes can be configured to use [[chunking]]. A max of one chunk will then be buffered in memory at a time. + +For example, to reconfigure an existing mys3 remote: `enableremote mys3 chunk=1MiB` +"""]] |