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

Hadoop QA commented on ZOOKEEPER-486:
-------------------------------------

+1 overall.  Here are the results of testing the latest attachment 
  http://issues.apache.org/jira/secure/attachment/12427942/ZOOKEEPER-486.patch
  against trunk revision 889848.

    +1 @author.  The patch does not contain any @author tags.

    +1 tests included.  The patch appears to include 6 new or modified tests.

    +1 javadoc.  The javadoc tool did not generate any warning messages.

    +1 javac.  The applied patch does not increase the total number of javac 
compiler warnings.

    +1 findbugs.  The patch does not introduce any new Findbugs warnings.

    +1 release audit.  The applied patch does not increase the total number of 
release audit warnings.

    +1 core tests.  The patch passed core unit tests.

    +1 contrib tests.  The patch passed contrib unit tests.

Test results: 
http://hudson.zones.apache.org/hudson/job/Zookeeper-Patch-h8.grid.sp2.yahoo.net/87/testReport/
Findbugs warnings: 
http://hudson.zones.apache.org/hudson/job/Zookeeper-Patch-h8.grid.sp2.yahoo.net/87/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output: 
http://hudson.zones.apache.org/hudson/job/Zookeeper-Patch-h8.grid.sp2.yahoo.net/87/console

This message is automatically generated.

> Improve bookie performance for large number of ledgers
> ------------------------------------------------------
>
>                 Key: ZOOKEEPER-486
>                 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-486
>             Project: Zookeeper
>          Issue Type: Improvement
>          Components: contrib-bookkeeper
>            Reporter: Flavio Paiva Junqueira
>            Assignee: Benjamin Reed
>         Attachments: ZOOKEEPER-486.patch, ZOOKEEPER-486.patch
>
>
> If we write simultaneously to a large number of ledgers on a bookie, then 
> performance drops significantly due to more seeks on the ledger device. In 
> such cases, we should be clustering ledgers into files to reduce the number 
> of seeks, and performing sequential writes on each file. Clustering ledgers 
> will impact read performance, so we would to have a knob to control such a 
> feature.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to