MAPI of Outlook 2019 does not perform as well as Outlook 2010

%3CLINGO-SUB%20id%3D%22lingo-sub-1856605%22%20slang%3D%22en-US%22%3EMAPI%20of%20Outlook%202019%20does%20not%20perform%20as%20well%20as%20Outlook%202010%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-1856605%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20are%20working%20on%20an%20archival%20solution.%20We%20have%20Microsoft%20Exchange%20as%20one%20of%20the%20supported%20sources%20from%20which%20documents%20are%20archived%20to%20a%20storage%20repository.%20Our%20application%20requires%20Outlook%20to%20be%20installed%20on%20the%20same%20server%20and%20uses%20MAPI%20for%20communication%20with%20the%20Exchange%20Server%20(On-Premises).%20We%20have%20a%20couple%20of%20queries%20related%20to%20MAPI%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3COL%3E%3CLI%3EWe%20ran%20a%20performance%20test%20with%20our%20application%20along%20with%20Outlook%202010%20vs%20Outlook%202019%2C%20both%20connected%20to%20an%20on-prem%20Exchange%202016%20Server.%20We%20saw%20that%20the%20rate%20of%20archival%20when%20using%20Outlook%202010%20client%20was%2074.9%20mails%2Fmin%20and%20when%20used%20with%20Outlook%202019%20was%20only%2036.5%20mails%2Fmin.%20The%20environment%20details%20in%20both%20were%20the%20same%20except%20for%20the%20outlook%20client%20used.%20Since%20the%20MAPI%20dlls%20are%20provided%20by%20the%20Outlook%20Client%2C%20we%20wanted%20to%20know%20if%20there%20are%20any%20differences%20in%20MAPI%20of%20Outlook%202010%20vs%20Outlook%202019%20that%20could%20manifest%20as%20this%20performance%20difference%3F%3C%2FLI%3E%3CLI%3EWe%20have%20tried%20using%20the%20MFCMAPI%20tool%20to%20compute%20some%20time%20durations%20for%20operations%20like%20%22Display%20Attachment%20Table%22%20and%20%22Display%20Recipient%20Table%22.%20Attaching%20a%20spreadsheet%20with%20our%20results.%20Please%20note%20that%20we%20have%20used%20Debug%20flag%200x40000000%20to%20only%20list%20the%20MAPIFunctions%20in%20MFCMAPI%20tool%20and%20Execution%20time%20calculated%20as%20the%20difference%20in%20Timestamps%20between%20first%20call%20OpenProperty%20and%20last%20call%20QueryRows.%20Is%20there%20any%20way%20workaround%2Fcircumvention%20for%20improving%20the%20response%20time%20in%20Outlook%202019%3F%3C%2FLI%3E%3CLI%3EAre%20there%20any%20particular%20debugging%20tools%20that%20can%20be%20used%20to%20further%20diagnose%20the%20performance%20difference%3F%3C%2FLI%3E%3C%2FOL%3E%3CP%3EAny%20suggestions%2Fpointers%20on%20the%20above%20would%20be%20highly%20appreciated!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-1856605%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EExchange%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOutlook%20for%20Windows%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Occasional Visitor

Hi,

 

We are working on an archival solution. We have Microsoft Exchange as one of the supported sources from which documents are archived to a storage repository. Our application requires Outlook to be installed on the same server and uses MAPI for communication with the Exchange Server (On-Premises). We have a couple of queries related to MAPI:

 

  1. We ran a performance test with our application along with Outlook 2010 vs Outlook 2019, both connected to an on-prem Exchange 2016 Server. We saw that the rate of archival when using Outlook 2010 client was 74.9 mails/min and when used with Outlook 2019 was only 36.5 mails/min. The environment details in both were the same except for the outlook client used. Since the MAPI dlls are provided by the Outlook Client, we wanted to know if there are any differences in MAPI of Outlook 2010 vs Outlook 2019 that could manifest as this performance difference?
  2. We have tried using the MFCMAPI tool to compute some time durations for operations like "Display Attachment Table" and "Display Recipient Table". Attaching a spreadsheet with our results. Please note that we have used Debug flag 0x40000000 to only list the MAPIFunctions in MFCMAPI tool and Execution time calculated as the difference in Timestamps between first call OpenProperty and last call QueryRows. Is there any way workaround/circumvention for improving the response time in Outlook 2019?
  3. Are there any particular debugging tools that can be used to further diagnose the performance difference?

Any suggestions/pointers on the above would be highly appreciated!

 

Thanks!

0 Replies