Renaming a layer in the current MXD should be instantaneous. After all the MXD will be in memory.This took 312 milliseconds.I think that having things on a network will be the likely culprit. It could be a very slow licence manager lookup causing the delay. Try a ping and other network analysis tools.I am amazed at the lengths people go to to avoid a simple local machine running Windows with local disks. They surely are a commodity? This is the only way I run processes for GIS analysis.Anything else is asking for much delay, even network calls are not optimised in any system, they simulate a local disk call, but are very slow across a network. Nothing to do with the network drives, its the OS and the network disconnection.Here is a benchmark script. I ran this in the Python window.>>> # rename layer
... import arcpy
... import datetime
... start = datetime.datetime.now()
... mxd = arcpy.mapping.MapDocument("CURRENT")
... lstDF = arcpy.mapping.ListDataFrames(mxd)
... print len(lstDF),"frames"
... for df in lstDF:
... print df.name
... llay = arcpy.mapping.ListLayers(mxd,"",df)
... for lay in llay:
... print lay.name
... print mxd.title,df.name,lay.name
... lay.name = lay.name+"changed"
... arcpy.RefreshActiveView()
... arcpy.RefreshTOC()
... print datetime.datetime.now() - start
...
2 frames
Layers
pointerchanged
topo250 Layers pointerchanged
coastlinechanged
topo250 Layers coastlinechanged
lakechanged
topo250 Layers lakechanged
native_polychanged
topo250 Layers native_polychanged
island_polychanged
topo250 Layers island_polychanged
mainlandchanged
topo250 Layers mainlandchanged
index250changed
topo250 Layers index250changed
Index
coastlinechanged
topo250 Index coastlinechanged
sheetchanged
topo250 Index sheetchanged
index250changed
topo250 Index index250changed
0:00:00.312000
