Calculating Geometry in ArcGIS Pro extremely slow

[ABishop]

Each time I attempt to calculate geometry for a feature class or shapefile, I experience extreme lag!  It doesn't matter if it is one record or 100 records... it is still slow.  Anybody else experiencing this?

[DanPatterson]

No, so you might want to look at

Announcing the ArcGIS Pro Performance Assessment Tool (PAT) (esri.com)

to see what is going on

[ABishop]

Thanks Dan.  I'll check it out.

[MichaelVolz]

What version of Pro are you seeing this slowness in?

Did you ever use this tool in an earlier version of Pro and get better results?

[ABishop]

2.8.2 and I just upgraded to 2.9

I installed the PAT tool that Dan suggested but I am lost on how to use it LOL.

I have performed the task in ArcMap and it didn't take half the time.

[MichaelVolz]

Are you specifically using the Calculate Geometry Attributes tool?

https://pro.arcgis.com/en/pro-app/2.8/tool-reference/data-management/calculate-geometry-attributes.h...

[ABishop]

No I was opening the attribute table and right clicking on the field then choosing calculate geometry.

I did it in ArcMap 10.5.1 and it took 26.04 seconds on 265,953 records

I did it in ArcGIS Pro 2.9 and it took 55.83 seconds on 26,953 records

I'll try the Calculate Geometry Attributes tool to see if there is a difference.

[ABishop]

I used that tool and there was only a 1 second difference in processing time.

[DanPatterson]

Which leaves...

Troubleshooting Performance Issues in ArcGIS Pro - Esri Community 

A first good place to start is with a locally saved table in a file geodatabase so that everything but your machine and your setup can be ruled out.

Also... don't compare Arcmap to Pro (the arcgis versions), it will only frustrate you.

Some of us in the Community used to compare the original ArcInfo and original Arcmap (pre arcgis) to the new fangled ArcGIS with similar complaints many years ago  😉 

[ABishop]

Yes I get it Dan!  I am working with a local cop of the data to perform the geoprocessing task.

In the scheme of things I know 55 seconds doesn't see long for that 200k+ of records but I have also see it happen with one record in an SDE environment.

I am an ArcMap 3.x baby so I get it... with each new development there are new headaches.  Overall I really like ArcGIS Pro so I'll just keep looking for improvements in later releases.

Happy Thanksgiving!