[
https://issues.apache.org/jira/browse/ZOOKEEPER-3180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16664257#comment-16664257
]
Fangmin Lv commented on ZOOKEEPER-3180:
---------------------------------------
Yes, it holds the serialized response, and re-uses that to serve all the read
requests until there is change invalidated that cache. So it can avoid
allocating and deserialize large response again and again, on our prod, we saw
some users are storing more than 4MB data in a single znode.
> Add response cache to improve the throughput of read heavy traffic
> -------------------------------------------------------------------
>
> Key: ZOOKEEPER-3180
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3180
> Project: ZooKeeper
> Issue Type: Improvement
> Components: server
> Reporter: Fangmin Lv
> Priority: Minor
> Fix For: 3.6.0
>
>
> On read heavy use case with large response data size, the serialization of
> response takes time and added overhead to the GC.
> Add response cache helps improving the throughput we can support, which also
> reduces the latency in general.
> This Jira is going to implement a LRU cache for the response, which shows
> some performance gain on some of our production ensembles.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
