Benchmark: FindIncludesInContent
Current Performance: 2,842 ns/op (2.84μs)
Historical Average: 2,409 ns/op (2.41μs)
Change: +17.9% slower
📈 Detailed Performance Metrics
Performance Comparison
- ns/op: 2,842 (was 2,409)
- Change: +17.9%
- Historical Data Points: 2
- Memory: 112 B/op
- Allocations: 3 allocs/op
Historical Data
| Date |
ns/op |
| 2026-04-30 |
2,471 |
| 2026-05-02 |
2,348 |
| 2026-05-03 |
2,842 |
Note: This benchmark is at nanosecond scale and may be subject to noise. Monitor for persistence across future runs.
💡 Recommended Actions
- Review recent changes to include-finding logic
- Monitor for persistence in upcoming daily runs before investigating deeply
- If persistent, use
go tool pprof to identify hotspots
📋 Additional Context
Automatically generated by Daily CLI Performance workflow
Generated by Daily CLI Performance Agent · ● 909K · ◷
Benchmark: FindIncludesInContent
Current Performance: 2,842 ns/op (2.84μs)
Historical Average: 2,409 ns/op (2.41μs)
Change: +17.9% slower
📈 Detailed Performance Metrics
Performance Comparison
Historical Data
Note: This benchmark is at nanosecond scale and may be subject to noise. Monitor for persistence across future runs.
💡 Recommended Actions
go tool pprofto identify hotspots📋 Additional Context
Automatically generated by Daily CLI Performance workflow