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 "Tellier Benoit (JIRA)" <se...@james.apache.org> on 2018/07/03 02:37:00 UTC
[jira] [Commented] (JAMES-2448) Camel container is too long to
start
[ https://issues.apache.org/jira/browse/JAMES-2448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16530730#comment-16530730 ]
Tellier Benoit commented on JAMES-2448:
---------------------------------------
https://github.com/linagora/james-project/pull/1512 proposes such changes.
Benefit: Camel boot time: 1s -> 200-250ms
No impact shown on mail delivery.
> Camel container is too long to start
> ------------------------------------
>
> Key: JAMES-2448
> URL: https://issues.apache.org/jira/browse/JAMES-2448
> Project: James Server
> Issue Type: Improvement
> Components: JMAP, SpoolManager & Processors, tests
> Reporter: Tellier Benoit
> Assignee: Antoine Duprat
> Priority: Major
>
> A classic mailet container takes up to 1 s to load on a warm JVM.
> Fast startup is critical for our testing strategy (relying heavily on integration tests). We should make camel container loading faster.
> Ideas:
> - Some parameters are passed to components via dynamically generated properties, on a per call basis. This is inefficient and can be passed by a constructor.
> - Many classes used in CamelMailetContainer are not static
> - We finally can heavily simplify the logic expressed in Camel DSL, and express it through a *split - process* way, instead of relying on *camel choices*.
> We should measure the effect on boot time, and run Gatling SMTP test to evaluate the impact on delivery.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org