tomoaki/hakmem
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: tone down Phase 75-5 PGO recovery estimates

Browse Source
This commit is contained in:
Moe Charm (CI)
2025-12-18 09:37:55 +09:00
parent e51231471b
commit d0cf0d6436
2 changed files with 5 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
docs/analysis/PERFORMANCE_TARGETS_SCORECARD.md
View File

@ -149,8 +149,8 @@ Phase 75-3 validated C5+C6 inline slots optimization on Standard binary (+5.41%)
2. **HIGH PRIORITY - PHASE 75-5 (PGO Profile Regeneration)** 2. **HIGH PRIORITY - PHASE 75-5 (PGO Profile Regeneration)**
- Regenerate PGO profile with C5=1, C6=1 training configuration - Regenerate PGO profile with C5=1, C6=1 training configuration
- Expected gain: +5-8% (if profile aligns with actual code optimization) - Expected gain: unknown (likely positive if the training profile matches the actual hot path, but not guaranteed)
- Estimated recovery: 55.51 M ops/s → ~58-59 M ops/s - Estimated recovery: treat any number as a hypothesis until re-measured (do not assume a return to Phase 69 levels)
- Root cause analysis: Investigate 14% gap vs Phase 69 (layout, code bloat, or profile mismatch) - Root cause analysis: Investigate 14% gap vs Phase 69 (layout, code bloat, or profile mismatch)
**Documentation:** **Documentation:**

6
docs/analysis/PHASE75_4_FAST_PGO_REBASE_RESULTS.md
View File

@ -6,7 +6,7 @@
**Key Finding**: C5+C6 inline slots optimization shows **+3.16% gain** on FAST PGO binary, meeting the ideal threshold but significantly lower than Standard's +5.41% gain. **Key Finding**: C5+C6 inline slots optimization shows **+3.16% gain** on FAST PGO binary, meeting the ideal threshold but significantly lower than Standard's +5.41% gain.
**Critical Concern**: FAST PGO baseline is **7.16% slower** than Standard baseline, suggesting potential PGO profile staleness or suboptimal training conditions. **Critical Concern**: FAST PGO baseline is **7.16% slower** than Standard baseline, suggesting potential PGO profile staleness, training mismatch, or build/layout drift.
--- ---
@ -155,7 +155,7 @@
3. **⚠ Regenerate PGO Profile** 3. **⚠ Regenerate PGO Profile**
- Train with C5=1, C6=1 (optimized config) - Train with C5=1, C6=1 (optimized config)
- Use Phase 75 codebase for profiling - Use Phase 75 codebase for profiling
- Expected result: close gap to Standard baseline - Expected result: uncertain; likely to improve if PGO was mismatched, but not guaranteed
4. **⚠ Root Cause Analysis: 14% Regression** 4. **⚠ Root Cause Analysis: 14% Regression**
- Compare Phase 69 vs Phase 75-4 binary characteristics - Compare Phase 69 vs Phase 75-4 binary characteristics
@ -176,7 +176,7 @@
7. **Standard vs FAST PGO Convergence** 7. **Standard vs FAST PGO Convergence**
- Investigate why Standard outperforms FAST PGO by 7-10% - Investigate why Standard outperforms FAST PGO by 7-10%
- Consider unified build configuration - Treat this as a measurement/forensics problem first (PGO profile, flags, link order), not an assumed “PGO must win” rule
- Document PGO ROI vs complexity cost - Document PGO ROI vs complexity cost
--- ---