[
https://issues.apache.org/jira/browse/JAMES-3487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17411605#comment-17411605
]
Benoit Tellier commented on JAMES-3487:
---------------------------------------
Hello,
Well this would in my opinion be a tremendeous task. In addition of defining
yet-another configuration file for a single configuration option, we would need
a factory to apply this configuration when instanciating MimeMessageWrapper
objects. Then we would need to use this factory in all places (likely also
change MimeMessageWrapper visibility to ensure we do not miss some). Likely a
change in the 200+ line of code.
To be faily honnest, I did not play enough with this configuration option to
identify a benefit worth the pain described above.
This code path have an history of using JVM flags (james.message.usememorycopy)
thus I wonder if with a well documented registry we could work around the
discoverability issues you mention.
Regards,
Benoit
> 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
> Time Spent: 40m
> Remaining Estimate: 0h
>
> 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]
