ArcGIS Pro Model Geoprocessing Slows Over Time

[NickWeil]

I am trying to make the switch to ArcGIS Pro (2.5.1) and am encountering what seem like very slow geoprocessing times. I built a very simple model that iterates through a feature dataset of ~900 feature classes (1 polygon in each) and buffers each one. The new feature class is written to another feature dataset in the same geodatabase.

When I kicked off this process, the iterate was taking ~6 seconds and the buffer took ~12. The process has been running for about 21 hours now and gotten through 600 feature classes, however the geoprocessing time has increased significantly. The iterate has stayed consistent, but the buffer operation now takes ~33 seconds!

I know there are faster ways to do this; my computer is a bit older (i7-6700 3.4 GHz, 32 GB RAM, 64 bit) and the data are stored across the network.

Overall, geoprocessing has seemed noticeably slow in Pro compared to similar operations in ArcMap. I haven't gotten to benchmark these tasks in ArcMap and don't have time to open a support ticket right now.

This post is not about bashing Pro, I'm just wondering if others have experienced this and what can be done to avoid it?

[NickWeil]

Thank you to everyone for their input on this post. I wanted to provide an update with the additional processing and testing that I performed over the weekend.

My initial buffer iteration completed after 32 hours. I moved all the data locally and started the next model (which is much more computationally intensive). This task iterated through all ~900 features in 3.75 hours.

In another test, I repeated the buffer iteration locally on a secondary PC with reduced specs (i7-4770 3.4 GHz, 16 GB RAM, 64 bit). This was finished in 3 hours.

Obviously processing over the network was the main issue in this situation. Generally, we have a very fast connection and there were no other large processing tasks happening at that time on our network. I will continue to test ArcGIS Pro in local processing vs. network processing, but as I said in a previous post, moving all data local for all processing is not a feasible solution.

[George_Thompson]

Thanks for the update. I know that doing GP processes over the network can cause it to be slower within ArcGIS Pro. There is a TON of communication happening.

It may be worth the investigation to talk to your network team to see is they have "limits" set on network traffic or noticed a huge spike and/or issues during that time frame. I have seen where the network will limit the traffic for one reason or another.