# Why is fetching dependencies with SwiftPM so slow?

**URL:** <https://forums.swift.org/t/why-is-fetching-dependencies-with-swiftpm-so-slow/67191>\
**Category:** Package Manager\
**Tags:** packagemanager\
**Created:** [September 8, 2023, 7:27pm UTC](https://forums.swift.org/t/why-is-fetching-dependencies-with-swiftpm-so-slow/67191 "2023-09-08T19:27:14Z")\
**Posts on this page:** 1\
**Showing post:** 10

<div class="post-metadata">

**Author:** ![NeoNacho](https://sea2.discourse-cdn.com/swift/user_avatar/forums.swift.org/neonacho/32/1368_2.png) [@NeoNacho](https://forums.swift.org/u/NeoNacho)\
**Post date:** [September 12, 2023, 4:50pm UTC](https://forums.swift.org/t/why-is-fetching-dependencies-with-swiftpm-so-slow/67191/10 "2023-09-12T16:50:00Z")

</div>

> [@jrose](#):
>
> I think I’m just missing something, but why would a registry help? Because there’s enough information available up front that shallow clones become an option again?

The registry spec has defined specific endpoints for querying and fetching package manifests (which are needed during package resolution, so potentially for many versions), so SwiftPM won't need to download the actual sources for a version until it has determined the concrete one to use.

---

_[View the full topic](https://forums.swift.org/t/why-is-fetching-dependencies-with-swiftpm-so-slow/67191)._
