nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

ArcGIS Pro - Python toolbox tools take a long time to run

JeremyBracone

Geoprocessing python tools from a python toolbox take a long time to start and then remain in the "Updating" phase after finishing for a long time (more than an hour). Even a default tool that does nothing takes a long time to run and remains in the "updating" state, sometimes not even finishing. I am running ArcGIS Pro 1.1 and am wondering what the problem might be.

This same python tool runs fine from ArcMap and also runs fine as a stand-alone script using the Python 3 interpreter.

I have had this same problem on multiple computers and had made ArcGIS Pro useless to me for running python tools.

Finde mehr Beiträge mit dem Tag

Accepted answers

JeremyBracone

We have identified what caused this behavior and will be submitting a bug report to ESRI.

There seems to be an issue with setting arcpy.env.addOutputsToMap to False in a python script tool. If that line is run in the python tool, tools will not complete after the script finishes. This behavior will persist for all geoprocessing script tools (and possibly normal gp tools) for the rest of the session.

Removing this line from all python toolboxes in the project and re-opening the project resolves the problem.

All comments

KevinGabelman

This is an older post, but I am having this issue with scripts that I run as Toolboxes. I am NOT using the arcpy.env.addOutputsToMap env at all.

I have a module that outputs time results for several tools and functions. The same tool in Arc, using only basic Python and arcpy modules, can take 2-5 times longer to run than when run from outside Arc on the same datasets.

The scripts themselves are around 1000 lines of code and contain multiple functions within one main class, as well as the "stopwatch" class and also, one "static tools" class that I use as a sort-of basic conversion calculator (get specs for a Feature Dataset; get needed standard spatial references; convert text to Bool; create a layer in-memory, etc).

What I am looking for, more than anything, is any advice or feedback that would tell me things like:

Does the length of a sub-functions code matter when maximizing Toolbox performance?
- e.g. is it better to split larger functions into smaller ones, or vice-versa?
Are there penalties for storing things in-memory (assuming we have plenty?)

Please, do not offer things like, "store your stuff locally." I know about this. All of these test scripts are running on a Threadripper + 3080, which has access to a dedicated write-drive and reads from an nvme RAID10 array.

JeremyBracone

Thanks for this tip.

JeremyBracone

We have identified what caused this behavior and will be submitting a bug report to ESRI.

Removing this line from all python toolboxes in the project and re-opening the project resolves the problem.

bharold

Hi, from the WAG department, go to the backstage and set Options>Geoprocessing 'Analyze script and model tools for ArcGIS Pro compatibility' to off. I have achieved faster startup times with this.

JeremyBracone

The problem seems isolated to my machines. I guess this means I might need to try resetting my application profile and as a last resort, reinstalling ArcGIS Pro to try to resolve the issue.

Thanks for everyone that provided feedback.

JeremyBracone

Logging in as a different user is my next test step. I have a colleague who has no issues running gp tools on their machine and will be testing their login on mine.

Are there account settings an admin can set that affects a user's ability to use custom geoprocessing tools?

DanPatterson_Retired

so that leaves your installation from my list. Does the same behaviour appear if logged in to your machine as a different user?

mvolz47

Sounds like you need to open a support incident

JeremyBracone

This was exactly the same python tool from a python toolbox in both versions. There was nothing that wasn't Python 3 compatible in the original python tool.

If I make a new python toolbox in Pro and run the default tool without any edits, parameters, or real code to run, I get the same behavior where it gets stuck after it completes and the geoprocessing dialog perpetually says "Updating...".

I get this problem with a default script tool in a conventional toolbox and with python toolboxes. The tool messages state that it completed...ArcPro seems to not to realize it.

mvolz47

Did you use the same Desktop python script in Pro? Or did you need to make some tweaks to deal with the python version difference?

DanPatterson_Retired

I haven't had this issue when

using a local install and a single use license
running with source and destination data on local machines
I manually updated python 2.7.x script to 3.4.x
I used a conventional toolbox

Not much help, but no speed issues in those circumstances, so at least you have the opportunity to narrow down the culprit.

Nimm an der Unterhaltung teil

Angemeldete Mitglieder können Beiträge verfassen, Updates folgen und mehr. Neu hier? Registriere ein kostenloses Konto.

Schnellzugriffe

Community Help
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.