mirror of
https://github.com/s3fs-fuse/s3fs-fuse.git
synced 2026-04-25 21:35:58 +03:00
[GH-ISSUE #368] Feature Request Content-Encoding:gzip #191
Labels
No labels
bug
bug
dataloss
duplicate
enhancement
feature request
help wanted
invalid
need info
performance
pull-request
question
question
testing
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/s3fs-fuse#191
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @lordtangent on GitHub (Feb 27, 2016).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/368
How about support for automatic gzip compression and tagging with Content-Encoding:gzip ?
That would reduce the file sizes for many common file types including executables.
@tspicer commented on GitHub (Mar 3, 2016):
+1
@RobbKistler commented on GitHub (Mar 4, 2016):
I suspect the mapping of file-like access to object access (ranged GET's, S3 multipart PUT's) makes this difficult.
@ggtakec commented on GitHub (Mar 6, 2016):
I think that it is difficult to dynamically compressed.
It is possible to compress upload after s3fs has accumulated in the temporary cache.
However, it is difficult to download.
Because if you want to download by specifying the offset, you have to decompress it after you download all.
And, I think this would be inefficient.
Therefore, I recommend that you compress the object before uploading it.
(I think that it is not good way to compress by s3fs.)
@ggtakec commented on GitHub (Mar 30, 2019):
We kept this issue open for a long time.
I will close this, but if the problem persists, please reopen or post a new issue.