We recently improved (in version 4.73.0)our cache storage solution, which can theoretically push and pull cache artifacts without application-level concurrency limits. This allows the system and transport layer to make optimal use of available network resources.
Since this theory needs validation, we’ve made the feature opt-in through feature flags. You can remove the limit by running tuist with the environment variable TUIST_CACHE_CONCURRENCY_LIMIT=none, or set a specific value like TUIST_CACHE_CONCURRENCY_LIMIT=20. If you’re using Mise, you can configure this in .mise.toml to enable it across all environments:
[env]
TUIST_CACHE_CONCURRENCY_LIMIT="none"
Could you enable this in your projects and let us know if you experience any performance improvements or issues? Thanks!