> Ah yes, compression and probably encryption will indeed preclude any
> sort of partial block caching. An implementation will have to be
> limited to plain uncompressed blocks, which is okay for my use-case
> though (borg provides its own encryption and compression anyway).
> [...]
Compression and encryption are integral parts of S3QL and I would argue
that disabling them is only an edge case.
I might be wrong but I think Nikolaus (maintainer of S3QL) will not
accept such a huge change into S3QL that is only beneficial for an edge
case.
Since you do not need compression and encryption (handled by borg
anyways) have you tried something with less abstractions?
Does https://github.com/kahing/goofys work for you? (maybe stack a
https://github.com/kahing/catfs on top)
--
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/d6b647d9-0bb1-1900-7c9e-8b7b9fa39624%40jagszent.de.
