After upgrading my IDM 4.5.5 test environment to IDM 4.7.2 and encountering no issues, I then upgraded my production environment exactly the same way. With IDM 4.5.5 in both environments and IDM 4.7.2 in my test environment, deploying a driver set with Designer only took about 35 seconds. In my production 4.7.2 environment Designer now takes a whopping 5 minutes!
If I deploy each of my five drivers individually they take approximately one minute each, so it's not one specific driver holding things up. I took a packet capture of the deploy and saw really slow LDAP search responses from the IDM engine server. I then noticed its ndsd process was pegged at 100% CPU utilization for the duration of the deployment and then drops back to normal. This issue does not occur in my test environment. Each environment is running the engine on a dedicated OES 2018 SP1 install, and are sharing the same Designer workspace as two separate projects on a Windows 10 workstation. I've since upgraded to IDM 4.7.3 and it's made no difference.
The only difference I can think of between my production and test IDM vaults is that one has 15,200 objects vs 40 objects. Is it normal for Designer 4.7 deployment to peg ndsd at 100% CPU and be really slow with this number of objects? If not, does anyone have any ideas or troubleshooting suggestions?
I've had a SR open on this for nearly two months with no response from Micro Focus except for initial contact the day I opened it, despite my pleas for troubleshooting assistance. My SR# is 101237767719.