prosgarz35 commented on PR #3193: URL: https://github.com/apache/james-project/pull/3193#issuecomment-5789217175
> > > > > > https://ci-builds.apache.org/job/james/job/ApacheJames/job/PR-3193/3/testReport/ > > > > > > Related errors on CassandraBlobIdRepairerIntegrationTest. Please help review and fix @HesandaLiyanage :) > > > > > > > > > > > > > > > Done!. `ChunkedBlobStoreDAO` returns slot content tagged with `ContentEncoding.ZSTD` (decompression is delegated to `ZstdBlobStoreDAO` in production). Updated `CassandraBlobIdRepairerIntegrationTest` to decompress the slot payload before asserting content equality. Both tests pass locally and checkstyle is clean. > > > > > > > > > > > > so now not James itself makes compression - now it doings S3 storage? > > > > > > > > > No, James itself still does all the compression. S3 is just an object store that receives and stores the bytes James sends it. > > > `ZstdBlobStoreDAO` (James) ➔ `ChunkedBlobStoreDAO` (James) ➔ `S3BlobStoreDAO` (S3) > > > > > > well i looking forward to move this task to RustFS S3 for example which can compress by myself with zstd/lz4, just as for me the more mail server dont do others jobs the better it doing main job - mail exchanging. > > yeah fair enough, and compression in james isn't forced either way, if the underlying s3 engine you're using already handles it at the storage layer, ceph or rustfs, you can just turn it off on the james side with blobstore.compression.enabled=false and let the backend do its thing. > > but for plain cloud s3 like aws, wasabi, backblaze b2 etc, none of those do any packing or compression on their own, so having james handle it out of the box still matters a lot there, otherwise your put costs and storage footprint climb pretty fast. yeah customizations always wins! so yeah for cloud its sure userful, also only zstd for now? i think in some cases lz4 needed (lower latency). And deduplication methods its like in ZFS? Just Windows Post-processing dedup wins for now. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
