Bug
Importing the ArcPy and the ArcGIS modules affect the performance of multiprocessing modules.
| Bug ID Number | BUG-000148712 |
|---|---|
| Submitted | April 22, 2022 |
| Last Modified | February 20, 2025 |
| Applies to | ArcGIS Pro |
| Version found | N/A |
| Operating System | N/A |
| Operating System Version | N/A |
| Status | As Designed |
Additional Information
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.Steps to Reproduce
Bug ID: BUG-000148712
Software:
- ArcGIS Pro
Get notified when the status of a bug changes
Discover more on this topic
Search for related information
Find training related to this topic
Explore ideas and give feedback
Get help from ArcGIS experts
Download the Esri Support App