[
https://issues.apache.org/jira/browse/JAMES-3487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17259642#comment-17259642
]
ASF GitHub Bot commented on JAMES-3487:
---------------------------------------
jeantil commented on pull request #285:
URL: https://github.com/apache/james-project/pull/285#issuecomment-755255428
>Could we have some real (aka Gatling) bench please? I'm feeling very
concerned by the potential impact on production.
can you detail your concerns ? as far as I can see the default has not
changed ...
in theory the computation of the value for threshold could have an impact
but it should get inlined pretty quickly since in a production setup the method
call is always going to return the same value
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> Configure MimeMessageInputStreamSource THRESHOLD
> ------------------------------------------------
>
> Key: JAMES-3487
> URL: https://issues.apache.org/jira/browse/JAMES-3487
> Project: James Server
> Issue Type: Improvement
> Components: James Core
> Reporter: Benoit Tellier
> Priority: Major
>
> This represents the point at which we should switch from a memory storage
> into a file storage.
> Defaults is 100 Kb.
> Obviously this parameter is important:
> - Higher values will operate mostly in-memory thus will have low latencies
> but will trash the heap and might trigger a GC hell.
> - Lower values will defensively operate on files. Higher latencies but
> predictable throughtput. Modern SSDs and FS cache should enable to keep up
> with high rates.
> Optimally we should have some bench showing the impact of this parameter.
> Related to JAMES-3477.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]