[
https://issues.apache.org/jira/browse/CAMEL-18494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17602494#comment-17602494
]
Claus Ibsen commented on CAMEL-18494:
-------------------------------------
You are welcome to work on a PR that allows to configure this buffer size
> camel-mllp - Allow the ability to set MIN_BUFFER_SIZE for SocketBuffer
> ----------------------------------------------------------------------
>
> Key: CAMEL-18494
> URL: https://issues.apache.org/jira/browse/CAMEL-18494
> Project: Camel
> Issue Type: New Feature
> Components: camel-mllp
> Affects Versions: 3.18.2
> Environment: Test environment: current environment is Camel / Quarkus
> Reporter: Joseph
> Priority: Minor
>
> When payloads are known to be always larger that the hardcoded
> MIN_BUFFER_SIZE of 2048, this results in the resizing of the buffer.
> [https://github.com/apache/camel/blob/c4b5791237bbf27af7b54bbd0d14b7c6944dff1f/components/camel-mllp/src/main/java/org/apache/camel/component/mllp/internal/MllpSocketBuffer.java#L39]
> There is also the belief that when a gc event occurs, the buffer then returns
> to the default size of MIN_BUFFER_SIZE, which again results in another
> resizing of the buffer when larger than MIN_BUFFER_SIZE payloads arrive.
> It is the hope that allowing for a customized MIN_BUFFER_SIZE would result in
> an overall faster sustained throughput when the payload size is known to be
> larger than MIN_BUFFER_SIZE (2048).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
