Improve comparison performance
If there is one thing that is :-( about Gearset is that for moderate size orgs (a few thousand objects), the default 64 comparison takes too long.
You want to initiate a deployment from source to target and, for whatever reason, you want to make sure you didn't miss anything that needs to be deployed
So, to be safe, you initiate the 64 default comparison.
And you wait (downloading, comparison). This can take several minutes. You go on to other tasks and your zeal to get the deployment done went off onto other things as the comparison time is too long to just wait and look at the screen.
Yes, I realize you can run reduced sets of comparisons to cut down on the number of objects but since the cost of forgetting an object is also high (during the actual validation/deployment). You'd rather be safe at the initial step.
No doubt making the comparison go faster has technical challenges but even 20-25% improvements would go a long way.
-
Erwin Will commented
When cloning the same package from production to multiple developer orgs it would be nice to save the cache the GitHub download so that you don't have to wait on Github.