zookeeper-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (Jira)" <j...@apache.org>
Subject [jira] [Commented] (ZOOKEEPER-3484) Improve the throughput by optimizing the synchronization around outstandingChanges
Date Tue, 10 Sep 2019 06:50:00 GMT

    [ https://issues.apache.org/jira/browse/ZOOKEEPER-3484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16926365#comment-16926365
] 

Hudson commented on ZOOKEEPER-3484:
-----------------------------------

SUCCESS: Integrated in Jenkins build ZooKeeper-trunk #686 (See [https://builds.apache.org/job/ZooKeeper-trunk/686/])
ZOOKEEPER-3484: Improve the throughput by optimizing the synchronizat… (hanm: rev dd96bec98db2b747958f9bcd0ea9f64d43eac17e)
* (edit) zookeeper-server/src/main/java/org/apache/zookeeper/server/ZooKeeperServer.java
* (edit) zookeeper-server/src/main/java/org/apache/zookeeper/server/FinalRequestProcessor.java


> Improve the throughput by optimizing the synchronization around outstandingChanges
> ----------------------------------------------------------------------------------
>
>                 Key: ZOOKEEPER-3484
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3484
>             Project: ZooKeeper
>          Issue Type: Improvement
>            Reporter: Yisong Yue
>            Assignee: Yisong Yue
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 3.6.0
>
>          Time Spent: 1h
>  Remaining Estimate: 0h
>
> The "processRequest(Request request)" function in FinalRequestProcessor.java synchronizes
around `outstandingChanges` for all requests now. However, this synchronization is unnecessary
for read requests, and skipping such synchronization for reads can improve the overall throughput
of the request processor pipeline.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

Mime
View raw message