In arcmap, calculate field is very fast. I'm the only one who have to wait forever to let pro do the same calculations?
By example, I have a table with 44 entry. Try to put 0 in the field rotation. The same calculation in arcmap, in basic, take seconds (less than 30s) but in Pro, after 20 min, still running with python or arcade.
What's strange is when I have to kill Pro, to continue working, the field is populated like if the geo processing is stuck.
Have you tried to run this operation in Pro on more than one computer? Do you have any other quirks in Pro that might indicate a clean install would be in order? (Machine or install test)
Have you tried to run this operation in Pro on a brand new project? (Project corruption test)
Maybe you can copy the data itself to a new source and see if the operation runs faster. (Data source corruption test)
Other tests to try/consider as my field calculations using ArcGIS Pro 2.9.2 and 3.0 are fast.
When you say "my field calculations using ArcGIS Pro 2.9.2 and 3.0 are fast." As these operations fast both locally and across a network or is there a big difference for you between these two scenarios?
Michael - my field calculations are local on disk and not on a network. Network bandwidth can affect ArcGIS Pro performance but I wouldn't think 20 minutes of lag/delay. In addition, I do my field calculations on fGDBs and eGDBs without latency (again, local on disk). I do not have access to a network drive for further testing. Is your data in question local on disk or a shared network drive?
Data are in FGDB stores in local HD. For me, the Calculated in Pro is always a pain in... v2 or v3 doesn't change anything. The window still open until I kill Pro to see the result. Like Pro (3,0,0) , for me, can't know the calculations is finished when I'm in a project.
Finally, stop using pro to do calculation. Made in 15 min all my calculations in arcmap on 8 fields where it's impossible in my project with Pro. Same data, the same location.
Try something to do a calculation in Pro for the same data but in a blank project. Work fine, faster than arcmap. I think the problem is that when you have a project (many maps, many layouts) pro is not made for that.
Have you thought about just having a GIS processing Pro project with a minimal amount of maps and layouts where you can perform faster processing than in ArcMap. Then just have data connections to the processed data in your Pro projects where you have layouts.