[
https://issues.apache.org/jira/browse/ZOOKEEPER-4717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Enrico Olivelli resolved ZOOKEEPER-4717.
----------------------------------------
Fix Version/s: (was: 3.8.2)
Resolution: Fixed
> Cache serialize data in the request to avoid repeat serialize.
> --------------------------------------------------------------
>
> Key: ZOOKEEPER-4717
> URL: https://issues.apache.org/jira/browse/ZOOKEEPER-4717
> Project: ZooKeeper
> Issue Type: Improvement
> Components: server
> Affects Versions: 3.8.1
> Reporter: Yan Zhao
> Assignee: Enrico Olivelli
> Priority: Minor
> Labels: pull-request-available
> Fix For: 3.9.0
>
> Time Spent: 2h
> Remaining Estimate: 0h
>
> For each request, it will be serialized three times.
> 1. Leader proposal. It will serialize the request, wrap the serialized data
> in a proposal, then send the proposal to the quorum members.
> 2. SyncRequestProcessor append txn log. It will serialize the request, then
> write the serialized data to the txn log.
> 3. ZkDataBase addCommittedProposal. It will serialize the request, wrap the
> serialized data in a proposal, then add the proposal to committedLog.
> Serialization operations are CPU-sensitive, and when the CPU experiences
> jitter, the time required for serialization operations will also skyrocket.
> Therefore, we should avoid serializing the same request multiple times.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
