You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by "ASF GitHub Bot (Jira)" <se...@james.apache.org> on 2021/01/02 06:55:00 UTC

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

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

ASF GitHub Bot commented on JAMES-3487:
---------------------------------------

chibenwa edited a comment on pull request #285:
URL: https://github.com/apache/james-project/pull/285#issuecomment-753440706


   I had been running a quick benchmark, sending 2000 mails of 100KB over 10 threads, on top of the distributed server. Here are the results:
   
   | Code version | master | #286         |
   |----------------|----------------|--------------------|
   | 1 byte threshold |       |      |
   | 100KB threshold |         |   162s |
   | 500 KB threshold |        |   |
   
   I did not manage to evaluate heap impact.


----------------------------------------------------------------
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:
users@infra.apache.org


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