You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@zookeeper.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2022/02/23 05:29:00 UTC

[jira] [Updated] (ZOOKEEPER-4476) Backport ZOOKEEPER-3179 for branch-3.5

     [ https://issues.apache.org/jira/browse/ZOOKEEPER-4476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

ASF GitHub Bot updated ZOOKEEPER-4476:
--------------------------------------
    Labels: pull-request-available  (was: )

> Backport ZOOKEEPER-3179 for branch-3.5
> --------------------------------------
>
>                 Key: ZOOKEEPER-4476
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-4476
>             Project: ZooKeeper
>          Issue Type: Improvement
>    Affects Versions: 3.5.9
>            Reporter: Ananya Singh
>            Assignee: Ananya Singh
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 3.6.0
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> When the snapshot becomes larger, the periodically snapshot after certain number of txns will be more expensive. Which will in turn affect the maximum throughput we can support within SLA, because of the disk contention between snapshot and txn when they're on the same drive.
>  
> With compression like zstd/snappy/gzip, the actual snapshot size could be much smaller, the compress ratio depends on the actual data. It might make the recovery time (loading from disk) faster in some cases, but will take longer sometimes because of the extra time used to compress/decompress.
>  
> Based on the production traffic, the performance various with different compress method as well, that's why we provided different implementations, we can select different compress method for different use cases.
>  



--
This message was sent by Atlassian Jira
(v8.20.1#820001)