| Table of Contents | ||||
|---|---|---|---|---|
|
Summary
Performance impact can come from a variety of sources, this page covers these, and may explain why JEMH works a particular way to minimise impact.
...
JEMH is a Mail Handler, with an Inbound Mail Server configuration in Jira, the JEMH Mail Handler selects a Configuration Profile to run with. The Jira scheduler manages when and where (DC only) the JEMH mail handler is invoked.
Problems with inbound mail
At the time JEMH is invoked, Jira has received a Memento of the email residing in the mailbox, such that only some core data is available, the mail does not exist ‘in full’ with Jira. As mailservers mail servers can close connections for a variety of reasons, when JEMH Auditing is enabled, JEMH will, before any processing, stream the entire email to disk as part of its auditing process. JEMH can be configured to reload this message from disk, in order to solve parsing problems with some email content, by doing this, there ends up being two copies of that message object in memory, a IO cost, but it ensure that mail that can be processed successfully, is.
...
The cause of the performance problem is too many concurrent conversations with incoming mailserversmail servers. JEMH solves this, primarily by allowing the ‘need’ for multiple actual mailboxes to be removed through the Project Mapping feature:
...
Considering it would not be possible to use hundreds of incoming mail handlers in Jira, JEMH offers a viable solution where it can be supported with minimal system impact whilst no mail is found as only one mailserver mail server connection is active.
Commenting
...