none
Improve Contact.Save/Update performance MS Exchange Server 2016 RRS feed

  • Question

  • Hello everyone,

    is there any way to improve the performance of the EWS managed api Contact.Save()/-Update() method on MS Exchange 2016 by throtteling?

    The following cmdlets didn't have any significant impact on the performance of the Contact.Save() method.

    Set-ThrottlingPolicy ConnectorPolicy
        -RCAMaxConcurrency Unlimited
        -EWSMaxConcurrency Unlimited
        -EWSMaxSubscriptions Unlimited
        -CPAMaxConcurrency Unlimited
        -EwsCutoffBalance Unlimited
        -EwsMaxBurst Unlimited
        -EwsRechargeRate Unlimited
        
    Set-Mailbox "Connector" -ThrottlingPolicy ConnectorPolicy

    Actually, it can save up to 4 contacts per second.

    Did I forget a parameter within the cmdlet?

    Thank you very much in advance.

    Monday, April 25, 2016 11:58 AM

All replies

  • Exchange no longer does micro delay throttling, meaning you will not see slowness as a result of a violated throttling policy. When throttling kicks in, you will get a 503 (ServerBusy) response.  The speed of saves depends on a lot of things, primarily what you are saving into the contact. 

    - Are you doing any MIME stuff?

    - Attachments?

    - Large Bodies ?

    - Are you batching these saves?

    - Are these CreateItem calls or UpdateItem calls?

    - What is the airspeed velocity of an unladen swallow?


    David Sterling http://www.microsoft.com/MSPress/books/10724.aspx

    Monday, April 25, 2016 5:38 PM
  • Thank you for replying.

    Our .net-application does only transfer basic fields like name, addresses, telephone numbers, fax etc.

    We do not handle attachments, lage bodies etc.

    We call the EWS managed api methods Contact.Save() and Contact.Update() which are similar to the EWS CreateItem and UpdateItem calls.

    Tuesday, April 26, 2016 9:55 AM
  • Hi,

    Are you using impersonation when you create the contacts ?

    If so, the used throttling policy is the one set on the impersonated mailbox and not the one you set.

    Regards,


    Désiré GOVIN Refresh IT Solutions

    Tuesday, April 26, 2016 10:54 AM
  • Hi,

    thank you for replying.

    The ConnectorPolicy was created for a specific mail account, which was intedetd for the use with the applications WCF service. It is the service account that is used by the .net-application to exchange contacts between our ERP-software and MS Exchange. So it should only affect this mail account.

    Best regards.

    EWSNewBie

    Monday, May 2, 2016 6:54 AM