[jira] [Updated] (BOOKKEEPER-461) Delivery throughput degrades when there are lots of publishers w/ high traffic.

["Sijie Guo (JIRA)" <ji...@apache.org>]

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

Sijie Guo updated BOOKKEEPER-461:
---------------------------------

    Attachment: BOOKKEEPER-461.patch

attach a new patch to stop putting entries to cache until old entries are collected.
                
> Delivery throughput degrades when there are lots of publishers w/ high traffic.
> -------------------------------------------------------------------------------
>
>                 Key: BOOKKEEPER-461
>                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-461
>             Project: Bookkeeper
>          Issue Type: Bug
>            Reporter: Sijie Guo
>            Assignee: Sijie Guo
>             Fix For: 4.2.0
>
>         Attachments: BOOKKEEPER-461.diff, BOOKKEEPER-461.diff, BOOKKEEPER-461.diff, BOOKKEEPER-461.patch, pub_sub_multithreads.png, pub_sub_singlethread.png
>
>
> When running benchmarking over the hub server, found that delivery throughput degrades when there are lots of publishers publishing messages. And the delivery throughput will goes up when there is no publishes.
> This issue is introduced due to ReadAheadCache only runs a single thread. So when the netty workers are busy handling publish requests, they are pushing lots of messages into ReadAheadCache's queue to put them in to read ahead cache. So the readahead cache is busy on updating keys.

--
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