locked
MIM 2016 SP2 Portal - SQL Performance RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello!

    I've patched a few environments to 4.6.263.0 and I've noticed really abysmal performance in the MIM-portal compared to 4.5.412.0 when writing changes to objects in the database.

    For test I added a a new bool to users that does nothing else. Changing this value in the portal will run up to 30 seconds.

    Sync engine seems to have equal performance as before.

    I've increased the timeouts so it seems that it runs ok but it just takes a lot longer time. Have anyone else experienced the same issues patching to SP2?


    Friday, September 25, 2020 7:15 AM

Answers

  • Question
    Sign in to vote
    3
    Sign in to vote
    After some quick testing there seemes to be much better performance in version 4.6.359.0! 
    • Proposed as answer by Borys Majewski Tuesday, December 1, 2020 12:31 PM
    • Unproposed as answer by Borys Majewski Tuesday, December 1, 2020 12:37 PM
    • Marked as answer by Viktor Nyberg Tuesday, December 1, 2020 12:41 PM
    Tuesday, December 1, 2020 8:58 AM

All replies

  • Question
    Sign in to vote
    1
    Sign in to vote

    I am also experiencing timeouts with my server which is also running MIM 2016 SP2 4.6.263.0. Earlier today while trying to run one of my scripts against the resource management URL, I got the following two messages in the order shown below:

    export-fimconfig : The request channel timed out while waiting for a reply after 00:01:29.9687427. Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding. The time allotted to this operation may have been a portion of a longer timeout.

    and then

    export-fimconfig : Connection to Resource Management Service at 'http://localhost:5725/resourcemanagementservice' ' has timed out.


    Friday, September 25, 2020 6:46 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    You might want to look at cleaning up old data.  Like clearing old run history, rebuilding or recreating indices, etc.

    https://social.technet.microsoft.com/wiki/contents/articles/2096.mim2016-how-to-use-powershell-to-delete-the-run-history-based-on-a-specific-date.aspx

    That should be a good start on clearing run history.  You can also do it through the sync console.

    If you noticed the problems immediately after an upgrade, then it might not be this kind of issue. But these can help a lot in general and you'd want to look at them after you get this acute issue resolved.

    Friday, November 20, 2020 2:04 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thanks for your reply. We generally keep 30-60 days in the sync and delete old run history with a scheduled script.

    I've also rebuild indexes and the full text catalog.

    We did experience the issues directly after the upgrade. We have a open case with Microsoft and I'll update here if we get a solution to the issue.

    Friday, November 20, 2020 2:46 PM
  • Question
    Sign in to vote
    1
    Sign in to vote
    I have a similar issue, applying hotfix to version 4.6.355.0 did not help. I also have a support case open and will provide an update here with any helpful information. 
    Sunday, November 22, 2020 11:24 PM
  • Question
    Sign in to vote
    3
    Sign in to vote
    After some quick testing there seemes to be much better performance in version 4.6.359.0! 
    • Proposed as answer by Borys Majewski Tuesday, December 1, 2020 12:31 PM
    • Unproposed as answer by Borys Majewski Tuesday, December 1, 2020 12:37 PM
    • Marked as answer by Viktor Nyberg Tuesday, December 1, 2020 12:41 PM
    Tuesday, December 1, 2020 8:58 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Yes,

    New MIM build 4.6.359.0 is available: Identity Manager version history | Microsoft Docs
    Replaces build 4.6.355.0 to address MIM Service performance issues.

    Borys Majewski, Identity Management Solutions Architect (Blog: IDArchitect.NET)

    • Proposed as answer by Borys Majewski Tuesday, December 1, 2020 12:37 PM
    • Unproposed as answer by Viktor Nyberg Tuesday, December 1, 2020 12:41 PM
    • Proposed as answer by Borys Majewski Wednesday, December 2, 2020 2:30 PM
    Tuesday, December 1, 2020 12:37 PM