I have a model that runs well for me. Just for fun (and to gain a lesson in Python) I exported the model to a .py file and ran it. The model runs in about 5 minutes while the Python script version takes about 20 minutes. Can anyone venture a guess as to why there is such a big difference? Could it be because of UNC path references?
Dan Patterson
hmmmm this also suggests issues... it is a medium sized read, but there are a few comments that may apply
arcgis 10.1 - Increasing speed of Python scripts using arcpy - Geographic Information Systems Stack Exchange
Joe, I can't comment on unc paths since I don't have the opportunity to use them. You should put in some timing steps before and after any path references to check. There are rumblings about python and unc paths
10.1. os.path — Common pathname manipulations — Python 2.7.12 documentation and again in python 3.5
11.2. os.path — Common pathname manipulations — Python 3.5.2 documentation so you will have to read the top of both sections to see if the reference is still the same.
but I bet it has something to do with backslashesesessess otherwise there wouldn't be support libraries out there
win_unc
Membros conectados podem postar, seguir atualizações e mais. Novo aqui? Registre uma conta gratuita.
Find useful guides, FAQs, and documents to help you navigate and make the most of Esri Community.
