You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@zookeeper.apache.org by "Flavio Paiva Junqueira (JIRA)" <ji...@apache.org> on 2010/03/13 15:25:27 UTC

[jira] Resolved: (ZOOKEEPER-486) Improve bookie performance for large number of ledgers

     [ https://issues.apache.org/jira/browse/ZOOKEEPER-486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Flavio Paiva Junqueira resolved ZOOKEEPER-486.
----------------------------------------------

       Resolution: Fixed
    Fix Version/s: 3.3.0

This issue has been fixed as part of the patch of ZOOKEEPER-507.

> 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
>             Fix For: 3.3.0
>
>         Attachments: ZOOKEEPER-486.patch, ZOOKEEPER-486.patch, ZOOKEEPER-486.patch, 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.