| Numéro d’ID de bogue |
BUG-000148712 |
| Envoi | April 22, 2022 |
| Dernière modification | February 20, 2025 |
| S’applique à | ArcGIS Pro |
| Version trouvée | N/A |
| Système d’exploitation | N/A |
| Version du système d’exploitation | N/A |
| Statut | As Designed
Après examen par l’équipe de développement, il a été déterminé que ce comportement est prévu. Pour plus d’informations, reportez-vous à la section Informations supplémentaires.
|
Informations supplémentaires
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.
Étapes pour reproduire
ID de bogue: BUG-000148712
Logiciel: