Ticket #284 (closed Defect: fixed)
Tools that do not have "Run Python script in process" checked run extremely slowly under ArcGIS 9.3
|Reported by:||jjr8||Owned by:||jjr8|
|Component:||Core - ArcGIS Interop||Version:|
These tools will generate the warning:
This tool may run slowly due to a geoprocessing performance degradation that ESRI introduced in ArcGIS 9.3. We are following up with ESRI about this problem and will try to get them to fix it. Please contact us if you have any questions. In the mean time, you can avoid this problem by running this tool on a computer with ArcGIS 9.1 or 9.2.
The problem is that ESRI degraded the performance of geoprocessing in 9.3 for out-of-process tools. In 9.1 and 9.2, all scripts ran out-of-process. In 9.3, ESRI introduced the in-process option. In-process tools in 9.3 run much faster than out-of-process tools in 9.1. or 9.2, so this option was a good improvement. But at the same time, ESRI appears to have degraded out-of-process performance.
For more information, see the thread I opened at the ESRI forums: http://forums.esri.com/Thread.asp?c=93&f=1729&t=264281&mc=0
There is no immediately obvious solution to this problem. I will follow up with ESRI about it. Based on past experience, I'm pretty sure they will refuse to fix it, in which case I'm not sure what I will do. The MGET scripts that run out-of-process do so with very good reason: they will not run in-process without making ArcCatalog or ArcMap unstable or otherwise breaking something. I will restructure as many as I can to run as in-process, but some will not be able to. If you have questions, please contact me.
You can avoid this problem by using Arc 9.1 or 9.2.