Download the PHP package nowo-tech/performance-bundle without Composer

Performance Bundle

⭐ Found this useful? Give it a star on GitHub! It helps us maintain and improve the project.

Symfony bundle for tracking and analyzing route performance metrics. Automatically records request time, database query count, and query execution time for performance analysis.

📋 Compatible with Symfony 7.x and 8.x - Requires PHP 8.2 or higher and Symfony 7.0 or higher.

This bundle is FrankenPHP worker mode friendly.

What is this?

This bundle helps you track and analyze route performance in your Symfony applications:

• 📊 Automatic Performance Tracking - Automatically tracks route performance metrics
• 🔍 Query Analysis - Counts and times database queries per route
• ⏱️ Request Timing - Measures request execution time
• 📈 Performance Analysis - Identifies slow routes and query-heavy endpoints
• 🎯 Route Metrics - Stores metrics per route and environment
• 🔧 Manual Updates - Command to manually set/update route metrics

Quick Search Terms

Looking for: route performance, performance monitoring, query tracking, Symfony performance, route metrics, performance analysis, database query tracking, request timing, profiling, performance bundle? You've found the right bundle!

Features

• ✅ Automatic route performance tracking via event subscribers
• ✅ Database query counting and execution time tracking
• ✅ Request execution time measurement
• ✅ Memory usage tracking - Track peak memory consumption per route
• ✅ Access frequency tracking - Track how often routes are accessed
• ✅ HTTP status code tracking - Track and calculate ratios for HTTP status codes (200, 404, 500, etc.)
• ✅ Sub-request tracking - Optional tracking of sub-requests (ESI, fragments, includes) in addition to main requests
• ✅ Performance notifications - Email, Slack, Teams, and webhook notifications for performance alerts
• ✅ Route data persistence in database
• ✅ Environment-specific metrics (dev, test, prod)
• ✅ Configurable route ignore list
• ✅ Command to manually set/update route metrics
• ✅ Support for multiple Doctrine connections
• ✅ Performance dashboard with filtering and sorting
• ✅ Data export - CSV and JSON export functionality
• ✅ Record management - Delete individual records (optional)
• ✅ Review system - Mark and edit records as reviewed with improvement tracking (optional)
• ✅ Bootstrap and Tailwind CSS support - Choose your preferred CSS framework
• ✅ Role-based access control for dashboard
• ✅ WebProfiler integration with ranking information
• ✅ Chart.js integration - Interactive performance charts
• ✅ Symfony UX Twig Components - Optional modern component system
• ✅ Nowo UiKit + FormKit — dashboard chrome and admin forms (nowo-tech/ui-kit-bundle, nowo-tech/form-kit-bundle, symfony/ux-icons)
• ✅ Symfony 7.x and 8.x compatible
• ✅ FrankenPHP — Compatible with FrankenPHP; production Caddyfile can use worker mode, while dev demos use APP_ENV=dev so the image entrypoint swaps in Caddyfile.dev (no worker, comfortable local dev). See docs/DEMO-FRANKENPHP.md and the demo READMEs.

Installation

Then, register the bundle in your config/bundles.php:

Quick Start

1. Configure the bundle (optional - works with defaults):

2. Create the database table(s):

   Option A: Using the bundle commands (Recommended):

   Option B: Using Doctrine Schema:

3. That's it! The bundle will automatically track route performance metrics in the configured environments.

For detailed installation steps (including sync-schema and migrations), see Installation Guide.

Requirements

• PHP >= 8.2, < 8.6
• Symfony 7.x or 8.x
• Doctrine ORM ^2.13 || ^3.0
• Doctrine Bundle ^2.8 || ^3.0 (3.0 required for Symfony 8)
• nowo-tech/form-kit-bundle ^2.2, nowo-tech/ui-kit-bundle ^1.4, symfony/ux-icons (dashboard UI)

Configuration

The bundle works with default settings. Create config/packages/nowo_performance.yaml. For the full reference and all options, see Configuration Guide.

Usage

Automatic Tracking

The bundle automatically tracks performance metrics for all routes (except ignored ones) in configured environments.

Manual Metrics Update

Use the command to inject sample metrics through the same PerformanceMetricsService pipeline as HTTP tracking (updates RouteData; may append RouteDataRecord rows when enable_access_records is enabled — same rules as live requests):

Accessing Metrics

Commands

See Commands for full documentation. Main commands:

• nowo:performance:create-table - Create or update the main metrics table (routes_data)
• nowo:performance:create-records-table - Create or update the access records table (routes_data_records); use when enable_access_records: true
• nowo:performance:sync-schema - Sync both tables with entity metadata (add/alter columns)
• nowo:performance:set-route - Set or update route performance metrics manually
• nowo:performance:diagnose - Diagnostic report of bundle configuration, tables, and tracking status
• nowo:performance:check-dependencies - Check status of optional dependencies (UX Icons, Messenger, Mailer)
• nowo:performance:purge-records - Purge old access records (by age or all)
• nowo:performance:rebuild-aggregates - Rebuild RouteData aggregates from access records

How It Works

1. Event Subscriber (PerformanceMetricsSubscriber) listens to kernel events
2. On KernelEvents::REQUEST, it starts tracking:
   • Request start time
   • Query tracking is initialized by QueryTrackingConnectionSubscriber (applies DBAL middleware and resets counters)
3. On KernelEvents::TERMINATE, it:
   • Calculates request time
   • Collects query count and execution time using multiple strategies:
   • Primary: QueryTrackingMiddleware (DBAL middleware for DBAL 3.x compatibility)
   • Fallback 1: DoctrineDataCollector from Symfony profiler
   • Fallback 2: Request attributes (_profiler, _profiler_profile)
   • Fallback 3: Stopwatch (time only)
   • Persists via PerformanceMetricsService: updates RouteData (identity + lastAccessedAt); when enable_access_records is on, inserts a RouteDataRecord for that request (subject to deduplication and per-route saveAccessRecords), unless metrics are recorded asynchronously (async: true with Messenger)

Query Tracking Architecture

The bundle uses a multi-layered approach for query tracking:

• QueryTrackingMiddleware: A custom DBAL middleware that intercepts all database queries at the driver level. This is the primary method and works with DBAL 3.x (which removed SQLLogger).
• DoctrineDataCollector: Falls back to Symfony's built-in profiler data collector if the middleware is not available.
• Request Attributes: Attempts to access profiler data from request attributes for sub-requests.
• Stopwatch: Last resort fallback for timing information only (does not provide query count).

This ensures reliable query tracking across different Symfony and Doctrine versions.

Screenshots

The bundle provides a web dashboard to monitor and analyze route performance. Below are the main views.

Performance Metrics Dashboard

The main dashboard shows KPIs (total routes, records, average/max queries and request time), top routes by usage and by latency, filters (environment, sort, limit), an optional “Optional Dependencies Missing” alert with composer require hints, a Performance Trends chart (average and max request time over days), and a Routes table with columns: route name, HTTP method, status codes, access count, environment, request time, query time, total queries, memory usage, last accessed at, access records link, and review status.

Access: dashboard path configured in nowo_performance.dashboard.path (e.g. /performance). Use Diagnose, Advanced Statistics, Export CSV/JSON, Access Statistics by Hour, and Clear All Records from the toolbar.

Advanced Performance Statistics

This view provides statistical analysis to find optimization targets: Performance Recommendations (e.g. high average query count, request time outliers), Correlation Analysis (request time vs query time, query time vs query count, memory vs request time), Efficiency Analysis (query time ratio), Traffic Distribution and hot/bad routes, Routes Needing Attention (high request time or query count by percentile), and detailed Request Time, Query Time, Query Count, Memory Usage, and Access Count sections with min/mean/median/max, percentiles, and distribution histograms.

Access: Advanced Statistics button from the main dashboard. Requires enough route data for meaningful stats.

Access Statistics by Hour

When temporal access records are enabled (enable_access_records: true), this page shows access patterns over time: filters (date range, environment, route, status code), Total Accesses and period, Statistics by Hour of Day (line chart: access count and average response time), Statistics by Day of Week and by Month (bar charts), Access Heatmap (day of week vs hour), and a detailed table by hour with access count, average response time, and status code breakdown. You can Delete records matching filter from here.

Access: Access Statistics by Hour from the main dashboard. Requires enable_access_records: true and the routes_data_records table (see Configuration).

Entity structure (v2.x)

Since 2.0.0, metrics are normalized: RouteData holds route identity and review metadata; per-request metrics live in RouteDataRecord (and dashboard/API use aggregates built from records). See ENTITY_NORMALIZATION_PLAN.md.

RouteData (routes_data) — one row per logical route + environment:

• id, env, name, httpMethod, params
• createdAt, lastAccessedAt
• Review: reviewed, reviewedAt, reviewedBy, queriesImproved, timeImproved
• saveAccessRecords — when access records are enabled globally, you can disable per-route record creation

RouteDataRecord (routes_data_records) — optional temporal log when enable_access_records: true (one row per request, deduplicated by request_id when set):

• Timing and load: responseTime, totalQueries, queryTime, memoryUsage, statusCode, accessedAt
• Context: route_params, route_path, referer, user_identifier, user_id, request_id

Listed metrics (request time, query counts, status code ratios, etc.) in the UI and exports are computed from records (or cached aggregates), not stored as scalar columns on RouteData.

Documentation

• GitHub Actions CI requirements
• Installation
• Configuration
• PSR evaluation (REQ-CS-007)
• Usage
• Contributing
• Code of Conduct
• Changelog
• Upgrading
• Release
• Security
• Engram
• Spec-driven development
• GitHub Spec Kit
• Roadmap

Additional documentation

• Demo with FrankenPHP (development and production)
• Commands
• Events & priorities
• Behaviour and notable changes
• Compatibility
• Notifications

Testing

Tests and coverage

• Tests: PHPUnit (PHP)
• PHP: ~99% lines (run make test-coverage for the current summary; badge rounded)

License

The MIT License (MIT). Please see LICENSE for more information.

Contributing

We welcome contributions! Please see CONTRIBUTING.md for details.

Author

Created by Héctor Franco Aceituno at Nowo.tech