topic Re: Execution time- Arcpy in Python Questions

Execution time- Arcpy

Yaron_YosefCohen — Sun, 12 Dec 2021 01:21:43 GMT

Hello everyone,

I am working on arcmap 10.3.1 and python 2.7.8. I need to determine how much time arcpy needed to finish a specific task (add layer) . I'm using this code:

import arcpy,os,sys,string,datetime,timeit
import arcpy.mapping
from arcpy import env

env.workspace = r"C:\Project"
Layer1 = arcpy.mapping.Layer(r"C:\Project\layers\atikot.lyr")
counter = 0
for mxd in arcpy.ListFiles("*.mxd"):
    print (mxd)
    mapdoc = arcpy.mapping.MapDocument(r"C:\Project\\" + mxd)
    df = arcpy.mapping.ListDataFrames(mapdoc, "Layers")[0]  
    arcpy.mapping.AddLayer(df ,Layer1, "TOP")
    print ('AddLayer')
    mapdoc.save()
    counter = counter + 1
del mxd 
print (counter)
print str(datetime.datetime.now().date())
print time.clock()

When i run it i get:

>>> 
Project 2.mxd
AddLayer
Project.mxd
AddLayer
soil.mxd
AddLayer
soil_20008.mxd
AddLayer
ta34b_4.mxd
AddLayer
wells.mxd
AddLayer
6
2015-03-18
3.20723655198e-07
>>>

I have been unable to get execution times for the processes. when i measured this process with stopper -i got 9.6 second in real time

but in the code the score is 3.207. I dont know if 3.2 is seconds -and if it is that mean this time isn't right.

Any help would be great

Re: Execution time- Arcpy

DanPatterson_Retired — Sun, 12 Dec 2021 01:21:46 GMT

practice with your stop watch before you use the time function

copy and paste these in an interactive editor session

>>> import datetime
>>> now = datetime.datetime.now()  # wait a bit, then paste the next line
>>> later = datetime.datetime.now()
>>> # ... your code stuff here or nothing ...
>>> elapsed = later - now
>>> print elapsed
0:00:04.416000
>>>

Re: Execution time- Arcpy

DanPatterson_Retired — Sun, 12 Dec 2021 01:21:48 GMT

And for extra clarity... just substitute the nap_time line with your code block

#  time_timeit_sleep_demo.py
#  Dan.Patterson@carleton.ca
#
import time
import datetime
now = datetime.datetime.now()
#
nap_time = time.sleep(5)  # sleep time in seconds... change to test
#
later = datetime.datetime.now()
elapsed = later - now
print('Nap time was... {} seconds').format(elapsed)

Re: Execution time- Arcpy

Yaron_YosefCohen — Wed, 18 Mar 2015 10:11:01 GMT

Dan, the run time is acually less then in my watch timer- why is it?

Re: Execution time- Arcpy

DanPatterson_Retired — Wed, 18 Mar 2015 10:26:47 GMT

maybe computer clock speeds...don't know

Re: Execution time- Arcpy

Yaron_YosefCohen — Wed, 18 Mar 2015 11:29:28 GMT

thanks Dan

Re: Execution time- Arcpy

JamesCrandall — Sun, 12 Dec 2021 01:21:51 GMT

Implement a Timer class to reuse throughout the code base.

class Timer:    
    def __enter__(self):
        self.start = time.clock()
        return self
    def __exit__(self, *args):
        self.end = time.clock()
        self.interval = self.end - self.start

Simple to implement, especially when you wrap up your functions/code blocks into individual def's

def dftest():
    #some process wrapped up in this def()

#time the process
t = Timer()
with t:
    dftest()

print "The process took %.2f Milisecs. " % (t.interval)

Re: Execution time- Arcpy

Yaron_YosefCohen — Wed, 18 Mar 2015 13:54:12 GMT

where i implement your code in my code?

Re: Execution time- Arcpy

JamesCrandall — Sun, 12 Dec 2021 01:21:54 GMT

class Timer:    
    def __enter__(self):
        self.start = time.clock()
        return self
    def __exit__(self, *args):
        self.end = time.clock()
        self.interval = self.end - self.start
        
import arcpy,os,sys,string,datetime,timeit  
import arcpy.mapping  
from arcpy import env  

def mainProcess():
    env.workspace = r"C:\Project"  
    Layer1 = arcpy.mapping.Layer(r"C:\Project\layers\atikot.lyr")  
    counter = 0  
    for mxd in arcpy.ListFiles("*.mxd"):  
        print (mxd)  
        mapdoc = arcpy.mapping.MapDocument(r"C:\Project\\" + mxd)  
        df = arcpy.mapping.ListDataFrames(mapdoc, "Layers")[0]    
        arcpy.mapping.AddLayer(df ,Layer1, "TOP")  
        print ('AddLayer')  
        mapdoc.save()  
        counter = counter + 1  
    del mxd 
  
t = Timer()
with t:
    mainProcess()

print "The process took %.2f Milisecs. " % (t.interval)

Re: Execution time- Arcpy

JamesCrandall — Sun, 12 Dec 2021 01:21:56 GMT

This slight change should give you the time interval in seconds:

#adjust from miliseconds to seconds
print "The process took %.02f secs. " % (t.interval)

Re: Execution time- Arcpy

OwenEarley — Sun, 12 Dec 2021 01:21:59 GMT

I have found function decorators a useful way to do this kind of thing. A good starting guide on function decorators is available at simeonfranklin.com - Understanding Python Decorators in 12 Easy Steps!

Basically, you wrap your processing function inside a timer function. This can be done ad-hoc by pre-pending the function definition with a decorator name and the @ symbol:

import time
import inspect

def recordPerformance(func):
    def wrapper(*arg):
        t1 = time.clock()
        res = func(*arg)
        t2 = time.clock()
        print '%s, %0.2f' % (func.func_name, (t2-t1))
        return res
    return wrapper

def mainProcess():
    subProcess1()
    subProcess2()
    subProcess3()

@recordPerformance
def subProcess1():
    time.sleep(2)

@recordPerformance
def subProcess2():
    time.sleep(1)

@recordPerformance
def subProcess3():
    time.sleep(3)


mainProcess()

When you run this the result is:

subProcess1, 1.99
subProcess2, 1.01
subProcess3, 3.00

EDIT - fixed function names in output results.

This approach provides a lot of flexibility and is great for logging and performance timing.

Re: Execution time- Arcpy

Yaron_YosefCohen — Thu, 19 Mar 2015 07:00:38 GMT

thanks Owen, i will try it

Re: Execution time- Arcpy

Yaron_YosefCohen — Thu, 19 Mar 2015 07:36:30 GMT

thanks James, when i run your code i get exactly the same result (seconds) as the of Dan's code. acualy ,when i measured time with stopper it shoe 5 second more than arcpy- maybe it because py call all modules and then start to measured the time?

Re: Execution time- Arcpy

FredMitchell — Thu, 04 Apr 2024 16:02:08 GMT

Hi @DanPatterson_Retired,

Not sure if you're still monitoring this thread but just wanted to comment that the syntax for Python 3.x has changed since Print is now a function so the brackets have to change slightly:

print('Script Complete...run time was... {} seconds'.format(elapsed))

Figured I'd share this updated line here in case anyone else is trying to use it. Thanks for providing the original code block!