Importing the ArcPy and the ArcGIS modules affect the performance of multiprocessing modules.
上次发布: October 4, 2022ArcGIS Pro
漏洞 ID 编号
BUG-000148712
已提交
April 22, 2022
上次修改时间
February 20, 2025
适用范围
ArcGIS Pro
找到的版本
N/A
操作系统
N/A
操作系统版本
N/A
状态
As Designed
经开发团队审核,已确定此行为符合设计。 有关详细信息,请参阅“其他信息”部分。
附加信息
When using the Multiprocessing with a Pool object, Multiprocessing creates separate processes up to the process count specified. Similarly, for Process, it creates a separate process for each operation. Both ArcPy and ArcGIS API for Python import a significant number of libraries and Dynamic link-library (DLL)s, and import time can vary from a couple of seconds to 15+ seconds for a fully loaded deep learning environment with the Python API. Because of how multiprocessing works, every process created incurs this same cost. In real workflows, typically the import cost is low relative to the other actions of the script, and the cost is amortized in the Pool case in particular. But there are cases where avoiding using either Python API improves performance because of the associated import costs.