Profiling Laravel with Blackfire and Xdebug | Mohamed Said [ ![Mohamed Said](https://cdn.msaied.com/01KT78WE565VEMM3PSNQAAB0MH.png) Mohamed Said Laravel Backend Engineer ](https://msaied.com) [ Home ](https://msaied.com) [ Projects ](https://msaied.com/projects) [ Articles ](https://msaied.com/articles) [ Certificates ](https://msaied.com/certificates) [ Contact ](https://msaied.com#contact-section) [ ](https://github.com/EG-Mohamed) [ Home ](https://msaied.com) [ Projects ](https://msaied.com/projects) [ Articles ](https://msaied.com/articles) [ Certificates ](https://msaied.com/certificates) [ Contact ](https://msaied.com#contact-section) [ home ](https://msaied.com) [ articles ](https://msaied.com/articles) Blackfire & Xdebug Profiling in Laravel: Finding Real Bottlenecks in Production-Like Environments On this page 1. [ Why Guessing Is Expensive ](#why-guessing-is-expensive) 2. [ Xdebug: Cachegrind Traces for Local Deep Dives ](#xdebug-cachegrind-traces-for-local-deep-dives) 3. [ Reading the Call Graph ](#reading-the-call-graph) 4. [ Blackfire: Continuous Profiling Without the Noise ](#blackfire-continuous-profiling-without-the-noise) 5. [ Profiling Artisan Commands and Queue Jobs ](#profiling-artisan-commands-and-queue-jobs) 6. [ Practical Workflow: From Trace to Fix ](#practical-workflow-from-trace-to-fix) 7. [ Takeaways ](#takeaways) ![Blackfire & Xdebug Profiling in Laravel: Finding Real Bottlenecks in Production-Like Environments](https://cdn.msaied.com/393/a8dfc4ec52c4febc3ef41a491eb452ea.png) #laravel #performance #profiling #blackfire #xdebug Blackfire & Xdebug Profiling in Laravel: Finding Real Bottlenecks in Production-Like Environments ======================================================================================================= 8 Jul 2026 4 min read ![Mohamed Said](https://cdn.msaied.com/01KT78WE565VEMM3PSNQAAB0MJ.jpg) Mohamed Said Table of contents 1. [ 01 Why Guessing Is Expensive ](#why-guessing-is-expensive) 2. [ 02 Xdebug: Cachegrind Traces for Local Deep Dives ](#xdebug-cachegrind-traces-for-local-deep-dives) 3. [ 03 Reading the Call Graph ](#reading-the-call-graph) 4. [ 04 Blackfire: Continuous Profiling Without the Noise ](#blackfire-continuous-profiling-without-the-noise) 5. [ 05 Profiling Artisan Commands and Queue Jobs ](#profiling-artisan-commands-and-queue-jobs) 6. [ 06 Practical Workflow: From Trace to Fix ](#practical-workflow-from-trace-to-fix) 7. [ 07 Takeaways ](#takeaways) Why Guessing Is Expensive ------------------------- Every senior engineer has shipped a "performance fix" that moved the wrong metric. Profiling tools exist precisely to replace intuition with evidence. Laravel's expressive API makes it easy to accidentally stack middleware, fire dozens of events, or trigger N+1 queries inside a resource collection — none of which `dd(microtime())` will isolate cleanly. This article covers two complementary tools: **Xdebug** for deep local traces and **Blackfire** for continuous, low-overhead profiling in staging and CI. --- Xdebug: Cachegrind Traces for Local Deep Dives ---------------------------------------------- Xdebug's profiler writes Cachegrind files you load in QCacheGrind or PhpStorm's built-in viewer. Enable it only on demand to avoid constant overhead: ```ini ; php.ini / xdebug.ini xdebug.mode = profile xdebug.start_with_request = trigger xdebug.output_dir = /tmp/xdebug xdebug.profiler_output_name = cachegrind.out.%p.%t ``` Trigger a single request with the `XDEBUG_PROFILE` cookie or query parameter: ```bash curl -b 'XDEBUG_PROFILE=1' https://local.app/api/orders ``` Open the resulting file in QCacheGrind and sort by **Self Cost** — that column shows time spent *inside* a function excluding callees. A `PDOStatement::execute` call dominating the list is a clear N+1 signal. A `json_encode` spike inside a resource transform points at a serialisation problem. ### Reading the Call Graph The call graph view is more useful than the flat list for Laravel apps because the framework's call stack is deep. Look for: - **Wide fan-out nodes** — a single controller method calling 30+ distinct functions often means over-eager eager loading or too many service resolutions. - **Recursive loops** — Eloquent's `getRelationValue` appearing hundreds of times is the classic lazy-load signature. --- Blackfire: Continuous Profiling Without the Noise ------------------------------------------------- Blackfire instruments PHP at the C extension level and samples at a rate that keeps overhead under 1 ms for most requests. Its killer feature is **assertions** — you write performance budgets in `.blackfire.yaml` and fail CI when they regress. ```yaml # .blackfire.yaml tests: "Order list endpoint stays fast": path: /api/orders assertions: - "main.wall_time < 200ms" - "metrics.sql.queries.count < 10" ``` Run a profile from the CLI against a staging environment: ```bash blackfire curl https://staging.app/api/orders ``` The output URL opens an interactive call graph in the Blackfire UI. The **Timeline** tab is the most actionable view for Laravel: it shows Illuminate bootstrap, middleware stack, controller, and response serialisation as horizontal bands. A thick `RouteServiceProvider` band usually means too many route model bindings resolving eagerly. ### Profiling Artisan Commands and Queue Jobs Blackfire wraps CLI processes too, which is invaluable for queue workers: ```bash blackfire run php artisan queue:work --once ``` This profiles a single job execution end-to-end. Combine it with a seeded job that exercises the hot path and you get reproducible traces you can compare across deploys. --- Practical Workflow: From Trace to Fix ------------------------------------- 1. **Reproduce in isolation.** Write a Pest test or a dedicated Artisan command that exercises only the slow path. Noise from other requests pollutes traces. 2. **Profile before touching code.** Resist the urge to add `with()` calls until the trace confirms the N+1. 3. **Fix one thing at a time.** Re-profile after each change. Two fixes applied together make it impossible to attribute the gain. 4. **Commit the Blackfire assertion.** Lock in the budget so the next engineer can't accidentally regress it. ```php // Before: triggers N+1 inside OrderResource public function toArray(Request $request): array { return [ 'id' => $this->id, 'customer' => $this->order->customer->name, // lazy load ]; } // After: eager load in the controller $orders = Order::with('customer')->paginate(); ``` The Blackfire timeline will show `metrics.sql.queries.count` drop from 51 to 2 — a concrete, shareable proof of the fix. --- Takeaways --------- - Use **Xdebug Cachegrind** for deep local investigation; sort by Self Cost to find hot functions. - Use **Blackfire** for staging and CI; its assertions turn performance budgets into failing tests. - Profile **queue jobs and Artisan commands**, not just HTTP endpoints. - Fix one bottleneck per profiling session and re-profile to confirm the gain. - Commit `.blackfire.yaml` assertions alongside the fix to prevent regression. Found this useful? [ ](https://twitter.com/intent/tweet?url=https%3A%2F%2Fmsaied.com%2Farticles%2Fblackfire-xdebug-profiling-in-laravel-finding-real-bottlenecks-in-production-like-environments&text=Blackfire+%26+Xdebug+Profiling+in+Laravel%3A+Finding+Real+Bottlenecks+in+Production-Like+Environments) [ ](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fmsaied.com%2Farticles%2Fblackfire-xdebug-profiling-in-laravel-finding-real-bottlenecks-in-production-like-environments) Frequently Asked Questions ---------------------------- 3 questions Q01 Can I use Blackfire in production without impacting users? Blackfire's overhead is low enough for production use when triggered manually via the browser extension or CLI, but most teams profile staging environments that mirror production data to avoid any risk to live traffic. Q02 What is the difference between Xdebug profiling and Blackfire? Xdebug writes full Cachegrind traces with exact call counts and inclusive/exclusive timings — great for deep local analysis but too heavy for continuous use. Blackfire samples at a lower overhead, integrates with CI via YAML assertions, and provides a hosted UI for comparing profiles across deploys. Q03 How do I profile a single Laravel queue job with Blackfire? Run `blackfire run php artisan queue:work --once` after pushing a known job onto the queue. Blackfire wraps the entire PHP process, so you get a full trace from worker bootstrap through job execution and teardown. Continue reading More Articles --------------- [ View all ](https://msaied.com/articles) [ ![HTTP Query Method Support in Laravel 13.19](https://cdn.msaied.com/394/4c917aad559beddb5eeb9a7a1e107f4c.png) Laravel Laravel 13 HTTP Client ### HTTP Query Method Support in Laravel 13.19 Laravel 13.19 adds Http::query() for the HTTP QUERY verb, query/queryJson testing helpers, a reduceInto() coll... ![Mohamed Said](https://cdn.msaied.com/01KT78WE565VEMM3PSNQAAB0MJ.jpg) Mohamed Said 8 Jul 2026 3 min read Read ](https://msaied.com/articles/http-query-method-support-in-laravel-1319) [ ![Laravel Cloud Security Defaults Behind Every Deploy](https://cdn.msaied.com/395/28df8f542fbe81ecee3ba4ad897f36d6.png) Laravel Cloud Security PHP ### Laravel Cloud Security Defaults Behind Every Deploy Laravel Cloud ships WAF rules, DDoS mitigation, automatic PHP patching, SOC 2 Type II compliance, and deploy-t... ![Mohamed Said](https://cdn.msaied.com/01KT78WE565VEMM3PSNQAAB0MJ.jpg) Mohamed Said 8 Jul 2026 4 min read Read ](https://msaied.com/articles/laravel-cloud-security-defaults-behind-every-deploy) [ ![Laravel Concurrency Facade and Process Pools for Parallel Work](https://cdn.msaied.com/392/fd3c54592355d96441888fa19c2674a0.png) laravel concurrency process ### Laravel Concurrency Facade and Process Pools for Parallel Work The Laravel Concurrency facade and Process pools let you run independent tasks in parallel without reaching fo... ![Mohamed Said](https://cdn.msaied.com/01KT78WE565VEMM3PSNQAAB0MJ.jpg) Mohamed Said 8 Jul 2026 3 min read Read ](https://msaied.com/articles/laravel-concurrency-facade-and-process-pools-for-parallel-work-3) [ ![Mohamed Said](https://cdn.msaied.com/01KT78WE565VEMM3PSNQAAB0MH.png) Mohamed Said Laravel Backend Engineer ](https://msaied.com)Senior Backend Engineer specializing in Laravel, scalable SaaS platforms, APIs, and cloud infrastructure. I build secure, high-performance web applications that help businesses grow. Explore - [Home](https://msaied.com) - [Projects](https://msaied.com/projects) - [Articles](https://msaied.com/articles) - [Certificates](https://msaied.com/certificates) - [Contact](https://msaied.com#contact-section) Connect - [ hello@msaied.com ](mailto:hello@msaied.com) - [ +20 109 461 9204 ](tel:+201094619204) © 2026 Mohamed Said. All rights reserved. [ ](https://github.com/EG-Mohamed) [ ](https://www.linkedin.com/in/msaiedm/) [ ](https://wa.me/201094619204) [ ](mailto:hello@msaied.com) [ ](https://drive.google.com/file/u/0/d/1MF20IPRJyzfy32mhEutjL5EpSls0w2Q8/view)