[performance] Regression in FindIncludesInContent: 50.5% slower

[github-actions]

📊 Performance Regression Detected

Benchmark: BenchmarkFindIncludesInContent

Current Performance: 50,715 ns/op (50.72µs)
Historical Average: 33,698 ns/op (33.70µs)
Change: +50.5% slower

📈 Detailed Performance Metrics

Performance Comparison

Metric	Current	Historical Avg	Change
ns/op	50,715	33,698	+50.5%
B/op	18,874	~33,698	—
allocs/op	61	—	—

Historical Data (3-day window)

Date	ns/op
2026-03-13	32,851
2026-03-14	34,544
2026-03-16	50,715 ⚠️

Baseline Targets

• FindIncludesInContent is a helper function used during workflow parsing
• Small absolute delta (~17µs), but significant relative change

💡 Recommended Actions

1. Review recent changes to FindIncludesInContent in pkg/workflow/ or related packages
2. Check if regex patterns or content parsing logic changed
3. Run make bench-memory to generate memory profiles
4. Use go tool pprof to identify hotspots: go test -bench=BenchmarkFindIncludesInContent -cpuprofile=cpu.prof ./pkg/...
5. Compare with previous benchmark results using benchstat

📋 Additional Context

• Run ID: §23149640600
• Date: 2026-03-16
• Threshold: Regressions flagged at >10% slower than 3-day rolling average
• Historical data points: 2
• Note: With only 3 benchmark iterations per run, results may have some variance. Consider monitoring next run to confirm.

---

Automatically generated by Daily CLI Performance workflow (§23149640600)

Generated by Daily CLI Performance Agent · ◷

• expires on Mar 18, 2026, 2:59 PM UTC