Long time to upload package
Last updated 2018-02-10 ·Reference W-3550470 ·Reported By 58 users
Some partner with large packages may notice it takes long time to upload a package.
The crux of the performance issues on the Package details page, which is the tabbed page from where a package upload is initiated, is what is called a Metadata Spider query. The metadata spider query is used to resolve dependent child metadata implicitly referenced by components explicitly added to the package (e.g. custom fields that are part of a custom object).
The metadata spider code is executed every time this page is loaded, and in some cases extraneously. When the “Upload” button is pushed, a message is pushed onto a queue for processing in the background. Once the message is picked up for processing, the metadata spider query is executed again, twice. For large packages with thousands of components, this query can take an unusual amount of time. Another factor that is likely contributing to the slowness and randomness of upload time is the underlying throttling of the message queue that’s processing the metadata spider query - due to its inefficiency.
1. In a DE org, create a package with thousands of components
2. Upload the package
No workaround at this point.
Safe Harbor: starting in the Spring ‘18 release, R&D team will work on resolving these performance issues including, but not limited to, optimizing when and how the metadata spider query is run and also optimizing the metadata spider query itself.
Reported By (58)
Is it Fixed?
Any unreleased services, features, statuses, or dates referenced in this or other public statements are not currently available and may not be delivered on time or at all. Customers who purchase our services should make their purchase decisions based upon features that are currently available.