docs: finalized wiki integrity maintenance (v3.0 standard) - pruned 1400+ stubs and fixed 11k+ ghost links

01_Archive/2026-04-20/InstancedMesh Performance Bottlenecks.md

@@ -1,13 +1,13 @@
 ---
 id: P-REINFORCE-AUTO-F035BF
-category: "[[10_Wiki/💡 Topics/Programming & Language]]"
+category: "10_Wiki/💡 Topics/Programming & Language"
 confidence_score: 0.90
 tags: [auto-reinforced]
 last_reinforced: 2026-04-20
 github_commit: "[P-Reinforce] Continuous Worker - InstancedMesh Performance Bottlenecks"
 ---
 
-# [[InstancedMesh Performance Bottlenecks]]
+# [[InstancedMesh Performance Bottlenecks|InstancedMesh Performance Bottlenecks]]
 
 ## 📌 한 줄 통찰 (The Karpathy Summary)
 > 지식 요약 정보 추출 중...
@@ -36,11 +36,11 @@ github_commit: "[P-Reinforce] Continuous Worker - InstancedMesh Performance Bott
 - **정책 변화:** Programming & Language 분야의 자동 자산화 수행.
 
 ## 🔗 지식 연결 (Graph)
-- **Related Topics:** [[Frustum Culling]], [[Overdraw]], [[Draw Call]], [[BatchedMesh]], [[Texture Atlas]]
-- **Projects/Contexts:** [[InstancedMesh2 library]], [[Three.js WebGPU Renderer]], [[WebGL multi_draw extension]]
+- **Related Topics:** [[Frustum Culling|Frustum Culling]], [[Overdraw|Overdraw]], [[Draw Call|Draw Call]], [[BatchedMesh|BatchedMesh]], [[Texture Atlas|Texture Atlas]]
+- **Projects/Contexts:** [[InstancedMesh2 library|InstancedMesh2 library]], [[Threejs WebGPURenderer|Three.js WebGPU Renderer]], WebGL multi_draw extension
 - **Contradictions/Notes:** 많은 렌더링 상황에서 `InstancedMesh`가 만능 최적화 기법으로 여겨지지만, 실제 벤치마크 사례에서는 드로우 콜을 1회로 줄였음에도 불구하고 오버드로우 및 GPU 프래그먼트 병목 때문에 개별 메쉬나 `BatchedMesh` 방식보다 오히려 렌더링 시간(Frame Time)이 느려지거나 성능이 저하되는 모순적인 결과가 발생하기도 합니다 [5, 6, 23].
 
 ---
 *Last updated: 2026-04-19*
-- Raw Source: [[00_Raw/2026-04-20/InstancedMesh Performance Bottlenecks.md]]
+- Raw Source: 00_Raw/2026-04-20/InstancedMesh Performance Bottlenecks.md
 ---