[
https://issues.apache.org/jira/browse/BOOKKEEPER-429?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Kelly updated BOOKKEEPER-429:
----------------------------------
Fix Version/s: (was: 4.2.0)
4.3.0
> Provide separate read and write threads in the bookkeeper server
> ----------------------------------------------------------------
>
> Key: BOOKKEEPER-429
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-429
> Project: Bookkeeper
> Issue Type: Improvement
> Components: bookkeeper-server
> Affects Versions: 4.2.0
> Reporter: Aniruddha
> Assignee: Aniruddha
> Fix For: 4.3.0
>
> Attachments: BK-429.patch
>
>
> The current bookkeeper server is single threaded. The same thread handles
> reads and writes. When reads are slow (possibly because of excessive seeks),
> add entry operations suffer in terms of latencies. Providing separate read
> and write threads helps in reducing add entry latencies and increasing
> throughput even when we're facing slow reads. Having a single read thread
> also results in low disk utilization because seeks can't be ordered
> efficiently by the OS. Multiple read threads would help in improving the read
> throughput.
> Discussion on this can be found at
> http://mail-archives.apache.org/mod_mbox/zookeeper-bookkeeper-dev/201209.mbox/%3ccaolhydqpzn-v10zynfwud_h0qzrxtmjgttx7a9eofohyyty...@mail.gmail.com%3e
> Reviewboard : https://reviews.apache.org/r/7560/
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
