Ensure both large repo and efficient CI advice are considered

doc/ci/large_repositories/index.md

@@ -5,11 +5,12 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 type: reference
 ---
 
-# Optimizing GitLab for large repositories
+# Optimize GitLab for large repositories **(FREE)**
 
 Large repositories consisting of more than 50k files in a worktree
-often require special consideration because of
-the time required to clone and check out.
+may require more optimizations beyond
+[pipeline efficiency](../pipelines/pipeline_efficiency.md)
+because of the time required to clone and check out.
 
 GitLab and GitLab Runner handle this scenario well
 but require optimized configuration to efficiently perform its

doc/ci/pipelines/pipeline_efficiency.md

@@ -28,6 +28,7 @@ The easiest indicators to check for inefficient pipelines are the runtimes of th
 stages, and the total runtime of the pipeline itself. The total pipeline duration is
 heavily influenced by the:
 
+- [Size of the repository](../large_repositories/index.md)
 - Total number of stages and jobs.
 - Dependencies between jobs.
 - The ["critical path"](#directed-acyclic-graphs-dag-visualization), which represents