[jira] [Commented] (JAMES-3487) Configure MimeMessageInputStreamSource THRESHOLD

["Benoit Tellier (Jira)" <se...@james.apache.org>]

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

Benoit Tellier commented on JAMES-3487:
---------------------------------------

https://www.mail-archive.com/server-dev@james.apache.org/msg71232.html

In the following email Otto proposes a configuration file to specify system properties used for James.

This ultimately leaves the use of System properties as an implementation detail to propagate this configuration (here it clearly is easier).

Here is what we wrote on the ML:

{code:java}
[...]

> # Extra system properties (S)
>
> Read a properties file immediately at server startup and set them as 
> system properties. Useful to keep command line clutter down and manageable.
+1

We had a recurring debate with @mbaechler on the use of system
properties within James.

On the one side there is the ease of use (no need to read a
configuration file, transform it in a POJO, and rely on abstract
factories etc to customise stuff).

On the other hand there are concerns around the discoverability of such
properties.

CF https://issues.apache.org/jira/browse/JAMES-3487

Maybe having this file would be a good place to document all those
properties (and make the use of System properties an implementation detail).

Would this suite you @mbaechler?

@Otto maybe we could have a list of the system properties you did find
useful? I think the community have limited knowledge regarding system
property usage with James... At least me...
[...]
{code}


> 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: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org