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

Hudson commented on ZOOKEEPER-3097:
-----------------------------------

SUCCESS: Integrated in Jenkins build ZooKeeper-trunk #122 (See 
[https://builds.apache.org/job/ZooKeeper-trunk/122/])
ZOOKEEPER-3097: Using Runnable instead of thread work items to improve (hanm: 
rev 75c652f45090f5309060ab7defb37f337d327d2c)
* (edit) src/java/main/org/apache/zookeeper/server/WorkerService.java


> Use Runnable instead of Thread for working items in WorkerService to improve 
> the throughput of CommitProcessor
> --------------------------------------------------------------------------------------------------------------
>
>                 Key: ZOOKEEPER-3097
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-3097
>             Project: ZooKeeper
>          Issue Type: Improvement
>          Components: server
>    Affects Versions: 3.6.0
>            Reporter: Fangmin Lv
>            Assignee: Fangmin Lv
>            Priority: Minor
>              Labels: performance, pull-request-available
>             Fix For: 3.6.0, 3.5.5
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> CommitProcessor is using this to submit read/write tasks, each task is 
> initialized as a thread, which is heavy, change it to a lighter Runnable 
> object to avoid the overhead of initializing the thread, it shows promised 
> improvement in the CommitProcessor.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to