I am using ArcGIS Pro 3.2. The Joins and Relates set up dialog performance is painfully slow to fill in the parameters. For example, I have an active map with 35 layers/Standalone tables it takes up to 2 minutes to populate the parameter drop downs listing the available layers/tables and fields. When the drop down options are available, the tool validation process virtually always resets all of my parameter choices back to the the original configuration when the tool opened approximately 4 times before it accepts my choices. It has at times forced me to choose the values I want up to 25 times for up to 4 more minutes. It seems to be stuck on validating the poorly constructed initial tool configuration it opened with which it can't satisfactorily complete before it takes any real input from me. The validation is excessive and unresponsive and its effort to autocomplete the parameters for me are all counter productive.
In the case of joins, I have had to wait up to 20 minutes for the joined table to refresh after completing the join on an SDE feature class and file geodatabase table with on 35K records in each and a one-to-one relationship. All other open tableviews become disabled for table navigation and selection while the join I created is refreshing.
Once the join of the 35 record tables was complete it took about 20 minutes to perform a simple selection query based on the join, even though the fields had attribute indexes. This whole process and poor performance repeatedly occurred in multiple exclusive fresh sessions of Pro. A field calculation also took 20 minutes.
This was repeated with other SDE to file geodatabase joins with different record set sizes and all have performed similarly poorly at every step in the joins process. Arcmap performed the entire set of tasks in under 4 minutes.
Activating a relate and getting the results also seems to take considerably longer than it does in ArcMap regardless of the size of the selection that activated the relate.
I agree that join performance in Pro should be re-evaluated, our team noticed such a drastic reduction in performance moving from Map to Pro that we now treat joins as a punishment for anyone who can't write Python scripts rather than a core ArcGIS function. We also use EGDBs extensively so I'd argue that's the best place to start looking for regressions.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.