[jira] [Commented] (FLUME-2233) MemoryChannel lock contention on every put due to bytesRemaining Semaphore

["Roshan Naik (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/FLUME-2233?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13813510#comment-13813510 ] 

Roshan Naik commented on FLUME-2233:
------------------------------------

whatever it is, it would be good to make it default. 
It would be nice to have most flume components require minimal (if not 0) explicit config tweaks to have them run in a performant manner.

> MemoryChannel lock contention on every put due to bytesRemaining Semaphore
> --------------------------------------------------------------------------
>
>                 Key: FLUME-2233
>                 URL: https://issues.apache.org/jira/browse/FLUME-2233
>             Project: Flume
>          Issue Type: Bug
>            Reporter: Hari Shreedharan
>            Assignee: Hari Shreedharan
>
> This semaphore is checked every time there is a put (unlike the queueRemaining semaphore which is checked only on transaction commits), causing the channel to slow down, even when the user does not care about memory usage. 
> We must add a new parameter to make sure that we look at bytesRemaining only when required which the user can disable if memory is not something they worry about because they know the channel size will be sufficiently small. By default, we will need to still check bytesRemaining to avoid breaking existing configurations.



--
This message was sent by Atlassian JIRA
(v6.1#6144)