[
https://issues.apache.org/jira/browse/BOOKKEEPER-656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13873567#comment-13873567
]
Sijie Guo commented on BOOKKEEPER-656:
--------------------------------------
[~fpj] all the changes are ready. 4 & 6 are already patch available. 7-9 is
related to the change of 1, as 1 is already in trunk. I don't see a reason to
leave 7-9 to next release. I would generate those patches after some of the
patch available tickets are in, so we don't have too much jiras pending on
review at a given time. does that make sense?
> Bookie Performance Improvement
> ------------------------------
>
> Key: BOOKKEEPER-656
> URL: https://issues.apache.org/jira/browse/BOOKKEEPER-656
> Project: Bookkeeper
> Issue Type: Improvement
> Components: bookkeeper-server
> Reporter: Sijie Guo
> Fix For: 4.3.0
>
>
> this is the master ticket to merge the bookie performance improvement made in
> twitter branch.
> it would generate the patches component by component (e.g. journal, ledger
> cache, entry logger)
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
