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) Profiling Laravel with Blackfire and Xdebug: Finding Real Bottlenecks On this page 1. [ Why "It Feels Slow" Is Not a Debugging Strategy ](#why-quotit-feels-slowquot-is-not-a-debugging-strategy) 2. [ Xdebug: Call-Graph Profiling Locally ](#xdebug-call-graph-profiling-locally) 3. [ What to Look For ](#what-to-look-for) 4. [ Blackfire: Timeline Profiling for Realistic Environments ](#blackfire-timeline-profiling-for-realistic-environments) 5. [ Reading the Call Graph ](#reading-the-call-graph) 6. [ Practical Workflow: Blackfire Assertions in CI ](#practical-workflow-blackfire-assertions-in-ci) 7. [ Combining Both Tools ](#combining-both-tools) 8. [ Takeaways ](#takeaways) ![Profiling Laravel with Blackfire and Xdebug: Finding Real Bottlenecks](https://cdn.msaied.com/334/7fd2cb3e1dda6c009d734cd376d14e36.png) #laravel #performance #blackfire #xdebug #profiling Profiling Laravel with Blackfire and Xdebug: Finding Real Bottlenecks ======================================================================= 1 Jul 2026 3 min read ![Mohamed Said](https://cdn.msaied.com/01KT78WE565VEMM3PSNQAAB0MJ.jpg) Mohamed Said Table of contents 1. [ 01 Why "It Feels Slow" Is Not a Debugging Strategy ](#why-quotit-feels-slowquot-is-not-a-debugging-strategy) 2. [ 02 Xdebug: Call-Graph Profiling Locally ](#xdebug-call-graph-profiling-locally) 3. [ 03 What to Look For ](#what-to-look-for) 4. [ 04 Blackfire: Timeline Profiling for Realistic Environments ](#blackfire-timeline-profiling-for-realistic-environments) 5. [ 05 Reading the Call Graph ](#reading-the-call-graph) 6. [ 06 Practical Workflow: Blackfire Assertions in CI ](#practical-workflow-blackfire-assertions-in-ci) 7. [ 07 Combining Both Tools ](#combining-both-tools) 8. [ 08 Takeaways ](#takeaways) Why "It Feels Slow" Is Not a Debugging Strategy ----------------------------------------------- Every Laravel app eventually develops a slow endpoint. The instinct is to add a cache layer or throw an index at the database. Sometimes that works. More often, you've optimised the wrong thing entirely. Profiling tools give you evidence before you act. This article focuses on two complementary tools: **Xdebug** for local call-graph analysis and **Blackfire** for timeline-based profiling in staging or production-like environments. --- Xdebug: Call-Graph Profiling Locally ------------------------------------ Xdebug's profiler writes a Cachegrind file you can open in KCachegrind (Linux) or QCachegrind (macOS/Windows). Enable it per-request so you don't drown in noise. ```ini ; php.ini or xdebug.ini xdebug.mode=profile xdebug.output_dir=/tmp/xdebug xdebug.profiler_output_name=cachegrind.out.%p.%r xdebug.start_with_request=trigger ``` Trigger a profile by appending `?XDEBUG_PROFILE=1` to any request, or set the cookie `XDEBUG_PROFILE=1` for a session. ```bash curl "http://localhost/api/reports?XDEBUG_PROFILE=1" \ -H "Authorization: Bearer $TOKEN" ``` Open the output file in QCachegrind and sort by **Self Cost**. You're looking for functions that consume time *excluding* their callees — those are the real culprits, not just the top of the call stack. ### What to Look For - `Illuminate\Database\Connection::select` called hundreds of times → N+1 query - `Illuminate\Container\Container::resolve` dominating → expensive service resolution on every request - `json_decode` / `serialize` in a hot loop → unnecessary (de)serialisation --- Blackfire: Timeline Profiling for Realistic Environments -------------------------------------------------------- Blackfire instruments PHP at the C extension level with near-zero overhead, making it safe for staging. Its timeline view maps wall-clock time across layers: PHP, SQL, HTTP calls, and cache. Install the agent and probe, then trigger a profile from the CLI: ```bash blackfire curl https://staging.example.com/api/reports \ -H "Authorization: Bearer $TOKEN" ``` Or use the browser extension for authenticated sessions. ### Reading the Call Graph Blackfire's call graph shows **inclusive time** (a node + all descendants) and **exclusive time** (the node alone). Focus on nodes with high exclusive time and low call count first — they're doing expensive work in a single shot. ```css App\Http\Controllers\ReportController::index 42ms (excl: 0.3ms) └─ App\Services\ReportBuilder::compile 41ms (excl: 38ms) ← HERE └─ Illuminate\Support\Collection::map 3ms ``` In this example, `ReportBuilder::compile` is doing 38 ms of work itself. Drilling in reveals it's calling `array_map` over a 10 000-row result set that should have been aggregated in SQL. --- Practical Workflow: Blackfire Assertions in CI ---------------------------------------------- Blackfire supports `.blackfire.yaml` assertions so slow regressions fail the build: ```yaml # .blackfire.yaml tests: "Report endpoint stays fast": path: "/api/reports" assertions: - "main.wall_time < 200ms" - "metrics.sql.queries.count < 10" ``` Pair this with `blackfire run php artisan test` to profile your test suite's critical paths without a browser. --- Combining Both Tools -------------------- Use Xdebug locally to explore unfamiliar code paths — the Cachegrind call graph is exhaustive. Switch to Blackfire when you need timeline context ("is this slow because of PHP or because of a slow query?") or when you want assertions in CI. Neither tool replaces the other. Xdebug is a microscope; Blackfire is a dashboard. --- Takeaways --------- - Enable Xdebug profiling per-request with `XDEBUG_PROFILE` triggers; never leave it on globally. - Sort Cachegrind output by **Self Cost** to find real hotspots, not just deep call stacks. - Blackfire's timeline separates PHP time from I/O time — essential for diagnosing slow queries vs. slow code. - Add `.blackfire.yaml` assertions to CI to catch performance regressions before they reach production. - High exclusive time + low call count = expensive single operation; high call count + low exclusive time = N+1 pattern. Found this useful? [ ](https://twitter.com/intent/tweet?url=https%3A%2F%2Fmsaied.com%2Farticles%2Fprofiling-laravel-with-blackfire-and-xdebug-finding-real-bottlenecks&text=Profiling+Laravel+with+Blackfire+and+Xdebug%3A+Finding+Real+Bottlenecks) [ ](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fmsaied.com%2Farticles%2Fprofiling-laravel-with-blackfire-and-xdebug-finding-real-bottlenecks) Frequently Asked Questions ---------------------------- 3 questions Q01 Can I use Blackfire on a production server without impacting users? Blackfire's overhead is low enough for production use when triggered selectively via the browser extension or CLI. Avoid enabling continuous profiling on every request; use targeted triggers instead. Q02 What is the difference between inclusive and exclusive time in a Blackfire call graph? Inclusive time includes the time spent in a function plus all functions it calls. Exclusive time is only the time spent inside that function itself. High exclusive time pinpoints where work is actually happening. Q03 Do I need both Xdebug and Blackfire, or is one enough? They serve different purposes. Xdebug gives a complete call graph ideal for local exploration. Blackfire provides timeline views, CI assertions, and lower overhead for staging environments. Using both gives you the full picture. Continue reading More Articles --------------- [ View all ](https://msaied.com/articles) [ ![Laravel 13: New Features, Helpers, and Practical Upgrade Notes](https://cdn.msaied.com/339/58c4fa6fe9b6d25a2dac17c621b6f4c6.png) laravel laravel-13 upgrade ### Laravel 13: New Features, Helpers, and Practical Upgrade Notes Laravel 13 ships with async-first defaults, a leaner bootstrapping layer, and several quality-of-life helpers.... ![Mohamed Said](https://cdn.msaied.com/01KT78WE565VEMM3PSNQAAB0MJ.jpg) Mohamed Said 1 Jul 2026 3 min read Read ](https://msaied.com/articles/laravel-13-new-features-helpers-and-practical-upgrade-notes) [ ![Laravel 12: Structured Route Files, Slim Skeletons, and the New Application Bootstrapping](https://cdn.msaied.com/337/05b39d16d0f88a5fb94d0cf74049b88b.png) laravel laravel-12 upgrade ### Laravel 12: Structured Route Files, Slim Skeletons, and the New Application Bootstrapping Laravel 12 ships with a leaner skeleton, first-class route file organisation, and a revised application bootst... ![Mohamed Said](https://cdn.msaied.com/01KT78WE565VEMM3PSNQAAB0MJ.jpg) Mohamed Said 1 Jul 2026 3 min read Read ](https://msaied.com/articles/laravel-12-structured-route-files-slim-skeletons-and-the-new-application-bootstrapping) [ ![Laravel API Resources: Sparse Fieldsets, Conditional Relationships, and Versioning](https://cdn.msaied.com/336/89d518450335e8fcdaa5be882cf4dd3e.png) laravel api resources ### Laravel API Resources: Sparse Fieldsets, Conditional Relationships, and Versioning Go beyond basic API resources. Learn how to implement sparse fieldsets, conditionally load relationships, and... ![Mohamed Said](https://cdn.msaied.com/01KT78WE565VEMM3PSNQAAB0MJ.jpg) Mohamed Said 1 Jul 2026 3 min read Read ](https://msaied.com/articles/laravel-api-resources-sparse-fieldsets-conditional-relationships-and-versioning) [ ![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)