Bug
Importing the ArcPy and the ArcGIS modules affect the performance of multiprocessing modules.
| Bug-ID-Nummer | BUG-000148712 |
|---|---|
| Eingereicht | April 22, 2022 |
| Zuletzt geändert | February 20, 2025 |
| Gilt für | ArcGIS Pro |
| Gefunden in Version | N/A |
| Betriebssystem | N/A |
| Betriebssystemversion | N/A |
| Status | As Designed |
Zusätzliche Informationen
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.Schritte zur Reproduzierung
Bug-ID: BUG-000148712
Software:
- ArcGIS Pro
Benachrichtigung erhalten, wenn sich der Status eines Bugs ändert
Weitere Informationen zu diesem Thema erkunden
Nach zugehörigen Informationen suchen
Nach Schulungen zu diesem Thema suchen
Ideen erkunden und Feedback geben
Unterstützung durch ArcGIS-Experten anfordern
Esri Support App herunterladen