wheels analyze performance

Analyzes application performance, identifying bottlenecks and optimization opportunities in your CFWheels application.

Usage

wheels analyze performance [--profile=<duration>] [--threshold=<ms>] [--format=<format>]

Parameters

• --profile - (Optional) Duration to profile the application (e.g., 30s, 5m). Default: 60s

• --threshold - (Optional) Minimum execution time in milliseconds to report. Default: 100

• --format - (Optional) Output format: console, json, csv. Default: console

Description

The analyze performance command profiles your CFWheels application to identify performance bottlenecks and provide optimization recommendations. It monitors:

• Request execution times

• Database query performance

• Memory usage patterns

• Cache effectiveness

• View rendering times

• Component instantiation overhead

Examples

Basic performance analysis

wheels analyze performance

Profile for 5 minutes

wheels analyze performance --profile=5m

Show only slow operations (>500ms)

wheels analyze performance --threshold=500

Export results as CSV

wheels analyze performance --format=csv > performance-report.csv

Output

The analysis provides:

• Slowest Requests: Top 10 slowest request paths

• Query Analysis: Slow queries and N+1 query detection

• Memory Hotspots: Areas of high memory allocation

• Cache Statistics: Hit/miss ratios for various caches

• Recommendations: Specific optimization suggestions

Sample Output

Performance Analysis Results
===========================

Slowest Requests:
1. GET /users/search (avg: 850ms, calls: 45)
2. POST /orders/create (avg: 650ms, calls: 12)
3. GET /reports/generate (avg: 1200ms, calls: 8)

Database Issues:
- N+1 queries detected in UsersController.index
- Slow query in Order.findRecent() - 450ms avg
- Missing index suggested for users.created_at

Memory Usage:
- High allocation in ReportService.generate()
- Potential memory leak in SessionManager

Recommendations:
1. Add eager loading to UsersController.index
2. Create index on users.created_at
3. Implement query result caching for Order.findRecent()

Notes

• Profiling adds minimal overhead to your application

• Best run in a staging environment with production-like data

• Can be integrated with APM tools for continuous monitoring

• Results are aggregated across all application instances