{"meta":{"title":"Caching repositories","intro":"You can improve performance for your geographically-distributed team with repository caching, which provides read-only mirrors close to your users and CI clients.","product":"Enterprise administrators","breadcrumbs":[{"href":"/en/enterprise-server@3.17/admin","title":"Enterprise administrators"},{"href":"/en/enterprise-server@3.17/admin/monitoring-and-managing-your-instance","title":"Monitor and manage your instance"},{"href":"/en/enterprise-server@3.17/admin/monitoring-and-managing-your-instance/caching-repositories","title":"Caching repositories"}],"documentType":"subcategory"},"body":"# Caching repositories\n\nYou can improve performance for your geographically-distributed team with repository caching, which provides read-only mirrors close to your users and CI clients.\n\n## Links\n\n* [About repository caching](/en/enterprise-server@3.17/admin/monitoring-and-managing-your-instance/caching-repositories/about-repository-caching)\n\n  You can increase the performance of Git read operations for distributed teams and CI farms with repository caching.\n\n* [Configuring a repository cache](/en/enterprise-server@3.17/admin/monitoring-and-managing-your-instance/caching-repositories/configuring-a-repository-cache)\n\n  You can configure a repository cache for GitHub Enterprise Server by creating a new instance, connecting the repository cache to your primary instance, and configuring replication of repository networks to the repository cache."}