-
Notifications
You must be signed in to change notification settings - Fork 48
Description
With the changes introduced in 5.1.0 (probably primarily #4046) the validation is now properly wired up. Some of these validations are quite compute intensive and lead to deteriorating the user experience.
Example profile of 5.0.5 of selecting a transport
Example profile of 5.1.1 selecting a transport
UsedPath validation can for example, take almost 2 seconds to enumerate the registry of all known instances, which causes the transport selection to hang noticeably.
This problem affects all input fields that have validation. You'll experience a significant slowdown even in port selection or name text boxes.
Describe the suggested solution
Some of the information we use in the validation can be cached and/or refreshed in the background. For all instance finding methods we can invalidate the cache when a new instance is added. Of course, if someone has SCMU open and installs things with powershell SCMU might not catch up but in the worst case we could invalidate all caches when someone explicitly hits the refresh button on SCMU


