[ZOOKEEPER-4717] Cache serialize data in the request to avoid repeat serialize.

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 3.8.1
• Fix Version/s: 3.9.0
• Component/s: server
• Labels: pull-request-available
• Assignee: Enrico Olivelli
• Reporter: Yan Zhao
• Created: 06/Jul/23 02:20
• Updated: 04/Aug/23 11:28
• Resolved: 13/Jul/23 06:18

Description

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.

Issue Links

• links to: GitHub Pull Request #2030