I'm curious, how long does it take in your machine(s) for your scripts to get ready to start working? Put something like this at the beginning of some scripts and share the results. from timeit import default_timer as timer start = timer ( ) from datetime import datetime , timedelta print ( '=== {}' . format ( datetime . now ( ) ) ) start_arc = timer ( ) import arcpy done_arc = timer ( ) - start_arc print ( '--- import arcpy overhead: {}' . format ( timedelta ( seconds = done_arc ) ) ) #import os, math, ... #carry on with your stuff elapsed_time = timedelta ( seconds = timer ( ) - start ) # get timer seconds and convert to hh:mm:ss print ( '=== Total Elapsed Time: {}' . format ( elapsed_time ) ) After about a week and perhaps 30 trials in various circumstances the fastest time I've ever seen is 7.8 seconds, the slowest is 10.5, and the median is ~8.5. (updated code to run in py 2.7 and 3.6+)

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; } } }

What is your "import arcpy" overhead?

MattWilkie1

I'm curious, how long does it take in your machine(s) for your scripts to get ready to start working?

Put something like this at the beginning of some scripts and share the results.

<SPAN class="keyword token">from</SPAN> timeit <SPAN class="keyword token">import</SPAN> default_timer <SPAN class="keyword token">as</SPAN> timer
start <SPAN class="operator token">=</SPAN> timer<SPAN class="punctuation token">(</SPAN><SPAN class="punctuation token">)</SPAN>
<SPAN class="keyword token">from</SPAN> datetime <SPAN class="keyword token">import</SPAN> datetime<SPAN class="punctuation token">,</SPAN> timedelta
<SPAN class="keyword token">print</SPAN><SPAN class="punctuation token">(</SPAN><SPAN class="string token">'=== {}'</SPAN><SPAN class="punctuation token">.</SPAN>format<SPAN class="punctuation token">(</SPAN>datetime<SPAN class="punctuation token">.</SPAN>now<SPAN class="punctuation token">(</SPAN><SPAN class="punctuation token">)</SPAN><SPAN class="punctuation token">)</SPAN><SPAN class="punctuation token">)</SPAN>

start_arc <SPAN class="operator token">=</SPAN> timer<SPAN class="punctuation token">(</SPAN><SPAN class="punctuation token">)</SPAN>
<SPAN class="keyword token">import</SPAN> arcpy
done_arc <SPAN class="operator token">=</SPAN> timer<SPAN class="punctuation token">(</SPAN><SPAN class="punctuation token">)</SPAN> <SPAN class="operator token">-</SPAN> start_arc

<SPAN class="keyword token">print</SPAN><SPAN class="punctuation token">(</SPAN><SPAN class="string token">'--- import arcpy overhead: {}'</SPAN><SPAN class="punctuation token">.</SPAN>format<SPAN class="punctuation token">(</SPAN>timedelta<SPAN class="punctuation token">(</SPAN>seconds<SPAN class="operator token">=</SPAN>done_arc<SPAN class="punctuation token">)</SPAN><SPAN class="punctuation token">)</SPAN><SPAN class="punctuation token">)</SPAN>

<SPAN class="comment token">#import os, math, ...</SPAN>
<SPAN class="comment token">#carry on with your stuff</SPAN>

elapsed_time <SPAN class="operator token">=</SPAN> timedelta<SPAN class="punctuation token">(</SPAN>seconds<SPAN class="operator token">=</SPAN>timer<SPAN class="punctuation token">(</SPAN><SPAN class="punctuation token">)</SPAN> <SPAN class="operator token">-</SPAN> start<SPAN class="punctuation token">)</SPAN>
    <SPAN class="comment token"># get timer seconds and convert to hh:mm:ss</SPAN>
<SPAN class="keyword token">print</SPAN><SPAN class="punctuation token">(</SPAN><SPAN class="string token">'=== Total Elapsed Time: {}'</SPAN><SPAN class="punctuation token">.</SPAN>format<SPAN class="punctuation token">(</SPAN>elapsed_time<SPAN class="punctuation token">)</SPAN><SPAN class="punctuation token">)</SPAN>‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍<SPAN class="line-numbers-rows"><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN><SPAN>‍</SPAN></SPAN>

After about a week and perhaps 30 trials in various circumstances the fastest time I've ever seen is 7.8 seconds, the slowest is 10.5, and the median is ~8.5.

(updated code to run in py 2.7 and 3.6+)

タグ付けされた投稿をもっと見る

Accepted answers

All comments

Anonymous User

Desktop 10.5 - concurrent license; Win 10 Enterprise x64, 64GB RAM; test through PyCharm

First run: 9.35 seconds

Second run: 3.86 seconds

Pro 2.4 - AGOL license; test through PyCharm

First run: 5.8 seconds

Second run: 4.3 seconds

CarlosSousaFerreira

Here are my results running from command line on Windows 10 Enterprise (64 bit); RAM: 8GB; Processor: Intel Core i#-6100 CPU @ 3.70GHz; ArcGIS Desktop 10.5.1 - License: Advanced (ArcInfo) Single Use

=== 2020-03-10 12:05:39.100000
--- import arcpy overhead: 0:00:02.663260
=== Total Elapsed Time: 0:00:02.666598

Surprised to see how it is a good result comparing with the other answers

MattAdams

Here are my results on Windows 10 running ArcGIS Pro 2.5:

=== 2020-03-09 16:22:25.363385
--- import arcpy overhead: 0:00:03.624114
=== Total Elapsed Time: 0:00:03.646515

MattWilkie1

There would be easier to track I think (and thanks in advance!)

DanPatterson_Retired

They may be in the arcgis module

Do you want the additions there? or here?

MattWilkie1

I updated the script so it outputs as a table, for easier comparison:

What is your "import arcpy" overhead? · GitHub

Does anyone know how to add what the license type and status is? (are we currently in mode "Single Use, Concurrent, Concurrent but Borrowed, AGOL, AGOL but Offline" etc.?)

And what about automatically appending to a public report Gist or similar?

DanPatterson_Retired

Cold start (both computer and operator)

Named User license

=== 2020-03-06 18:15:53.214205
--- import arcpy overhead: 0:00:07.948694
=== Total Elapsed Time: 0:00:07.949882

Spyder, kernel restart

=== 2020-03-06 18:17:48.751537
--- import arcpy overhead: 0:00:07.402486
=== Total Elapsed Time: 0:00:07.403328

Sadly, just about everything in the stream imports arcpy at some point

but if you just import what you need, you keep the namespace uncluttered.

Also, import python modules and other 3rd party modules "before" you import arcpy

My favorite... just run it again with no restart

=== 2020-03-06 18:19:29.711990
--- import arcpy overhead: 0:00:00.000067
=== Total Elapsed Time: 0:00:00.000738

bixb0012

That is interesting. Are you sure you aren't sitting in an Esri office somewhere...

JoeBorgione

after a machine restart:

=== 2020-03-06 15:30:26.956646
--- import arcpy overhead: 0:00:03.617659
=== Total Elapsed Time: 0:00:03.618505

which is still faster than I would have bet on. It always seems longer than that. Just restarted spyder and got:

=== 2020-03-06 15:33:50.404610
--- import arcpy overhead: 0:00:03.998263
=== Total Elapsed Time: 0:00:03.998689

interesting.....

bixb0012

You either had Pro open or was working with Pro earlier in the day. If you reboot and do a cold test, i.e., without having open Pro, I am guessing it will be noticeably longer.

JoeBorgione

I surprised to see:

=== 2020-03-06 15:20:12.398747
--- import arcpy overhead: 0:00:02.838384
=== Total Elapsed Time: 0:00:02.838892

It always seems much longer that that.

(arcgis Pro 2.5, advanced license as named user in agol...)

ShaneMiles222

Hi Matt Wilkie‌,

My results were:

=== 2020-03-06 15:15:35.488000
--- import arcpy overhead: 0:00:03.081489
=== Total Elapsed Time: 0:00:03.094335

Shane

bixb0012

On my local PC, ArcGIS Desktop 10.8 runs around 4 seconds while ArcGIS Pro 2.5 takes 14 seconds. The difference in times on my machine is easily explained by licensing mode/model. For ArcGIS Desktop 10.8 I am using Single-Use (which will be the fastest of any licensing model) while for Pro 2.5 I am using Named User licensing from AGOL. I am quite sure that Single Use licensing for Pro would put it down around 6 seconds or faster.

If you care about ArcPy startup times, it starts with sharing what your current licensing model is.

BenTurrell

Hey Matt Wilkie‌,

My results are:

=== 2020-03-06 09:54:51.555443
--- import arcpy overhead: 0:00:05.055231
=== Total Elapsed Time: 0:00:05.098868

Thanks,

Ben

If this answer has helpful please mark it as helpful. If this answer solved your question please mark it as the answer to help others who have the same question.

MattWilkie1

Oh wow, I want times like that. It's so annoying to wait 10 secs for startup and then have the real work happen in half that time. I wonder why mine is so much slower. What's your machine and how are you licensed (AGOL Named User, Concurrent, Single Use, Portal, ...)?

My machine:

Dell Precision Tower 7810
2 physical processors: Intel(R) Xeon(R) CPU E5-2620 v3 @ 2.40GHz, 2401 Mhz, 6 Core(s), 12 Logical Processor(s)

32 GB Ram

Win10 Enterprise x64, version 10.0.18362 Build 18362

C: and 😧 are Samsung SSD 840 EVO 500GB (SSD).

Licensing:

Pro: AGOL Named User

ArcMap: Concurrent license manager (in same building).

Pro's python 3.6 via Pyzo IDE:

--- import arcpy overhead: 0:00:09.052498

ArcMap's python 2.7 via Pyzo IDE:

--- import arcpy overhead: 0:00:06.414285

(I updated the code in first post so it will run in python 2.7 also)

DanPatterson_Retired

is everyone in a rush today

or is esri's "call home" slow today?

https://community.esri.com/thread/249381-strip-arcpy-libraries

blake.terhune

On Windows 10 with ArcGIS 10.5.1, run from VS Code

--- import arcpy overhead: 0:00:02.766314
=== Total Elapsed Time: 0:00:02.768425‍‍<SPAN class="line-numbers-rows"><SPAN>‍</SPAN><SPAN>‍</SPAN></SPAN>

会話に参加する

サインインしたメンバーは投稿、更新のフォローなどができます。初めてですか？無料アカウントを登録してください。

クイックリンク

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