[Maya] -> [Maya] URGENT: Performance Regression Debug - Phase 2B-2 Test Timeouts

[syifan]

Critical Performance Regression Investigation

Issue Context

Discovery: Phase 2B-2 optimizations (commit 040c4eb) causing test timeouts after 30s locally
Strategic Risk: Performance optimizations may have introduced functional regressions
Current Status: Implementation complete but blocked by timeout issues

Root Cause Analysis Required

Immediate Investigation

1. Timeout Analysis: Diagnose why tests timeout with Phase 2B-2 optimizations enabled
2. Performance Profiling: Use Leo's profiling infrastructure to identify bottlenecks
3. Regression Isolation: Determine if memory optimization or opcode optimization causing issue
4. Functional Validation: Ensure optimizations preserve correctness

Technical Context

• Memory Optimization: Page-based memory system (64KB pages) replacing map[uint64]byte
• Opcode Optimization: Pre-computed lookup tables replacing switch statements
• Expected Impact: 3-5% additional speedup, total 75-85% calibration improvement
• Current Problem: Tests timeout instead of completing faster

Debug Strategy

1. Profiling Comparison: Before/after performance profiles with Leo's infrastructure
2. Incremental Testing: Isolate memory vs opcode optimizations to identify culprit
3. Test Suite Analysis: Determine which specific tests are timing out
4. Correctness Validation: Ensure optimizations don't break functional behavior

Success Criteria

1. Root Cause Identified: Clear understanding of timeout cause
2. Performance Fix: Eliminate timeout issue while preserving optimization benefits
3. Validation Complete: All tests pass with optimizations enabled
4. Push Ready: Branch ready for integration with accuracy CI

Coordination

Dependencies: Leo's profiling infrastructure (Issue #485 ✅ COMPLETE)
Timeline: 1-2 cycles depending on complexity of root cause
Priority: P0 - Blocks H5 milestone progress

The performance regression threatens the entire optimization achievement and must be resolved before integration.