Profiling Laravel with Blackfire and Xdebug | Mohamed Said [ ![Mohamed Said](https://cdn.msaied.com/01KT78WE565VEMM3PSNQAAB0MH.png) Mohamed Said Laravel Backend Engineer ](https://www.msaied.com) [ Home ](https://www.msaied.com) [ Projects ](https://www.msaied.com/projects) [ Articles ](https://www.msaied.com/articles) [ Certificates ](https://www.msaied.com/certificates) [ Contact ](https://www.msaied.com#contact-section) [ ](https://github.com/EG-Mohamed) [ Home ](https://www.msaied.com) [ Projects ](https://www.msaied.com/projects) [ Articles ](https://www.msaied.com/articles) [ Certificates ](https://www.msaied.com/certificates) [ Contact ](https://www.msaied.com#contact-section) [ home ](https://www.msaied.com) [ articles ](https://www.msaied.com/articles) Profiling Laravel with Blackfire and Xdebug: Finding Real Bottlenecks On this page 1. [ Why "It Feels Slow" Is Not a Diagnosis ](#why-quotit-feels-slowquot-is-not-a-diagnosis) 2. [ Xdebug: Callgrind Profiles for Deep Call-Tree Analysis ](#xdebug-callgrind-profiles-for-deep-call-tree-analysis) 3. [ What to Look For in Laravel ](#what-to-look-for-in-laravel) 4. [ Blackfire: Timeline Profiling for Real-World Scenarios ](#blackfire-timeline-profiling-for-real-world-scenarios) 5. [ Combining Both Tools: A Practical Workflow ](#combining-both-tools-a-practical-workflow) 6. [ A Real Example: Slow Report Endpoint ](#a-real-example-slow-report-endpoint) 7. [ Takeaways ](#takeaways) ![Profiling Laravel with Blackfire and Xdebug: Finding Real Bottlenecks](https://cdn.msaied.com/712/7fd2cb3e1dda6c009d734cd376d14e36.png) #laravel #performance #blackfire #xdebug #profiling Profiling Laravel with Blackfire and Xdebug: Finding Real Bottlenecks ======================================================================= 28 Sep 2026 4 min read ![Mohamed Said](https://cdn.msaied.com/01M22N44A70A5MC2S599JP0MPH.webp) Mohamed Said Table of contents 1. [ 01 Why "It Feels Slow" Is Not a Diagnosis ](#why-quotit-feels-slowquot-is-not-a-diagnosis) 2. [ 02 Xdebug: Callgrind Profiles for Deep Call-Tree Analysis ](#xdebug-callgrind-profiles-for-deep-call-tree-analysis) 3. [ 03 What to Look For in Laravel ](#what-to-look-for-in-laravel) 4. [ 04 Blackfire: Timeline Profiling for Real-World Scenarios ](#blackfire-timeline-profiling-for-real-world-scenarios) 5. [ 05 Combining Both Tools: A Practical Workflow ](#combining-both-tools-a-practical-workflow) 6. [ 06 A Real Example: Slow Report Endpoint ](#a-real-example-slow-report-endpoint) 7. [ 07 Takeaways ](#takeaways) Why "It Feels Slow" Is Not a Diagnosis -------------------------------------- Every senior engineer has inherited a Laravel app where someone added a cache layer to a symptom rather than fixing the cause. Profiling tools exist precisely to replace intuition with evidence. Blackfire and Xdebug serve different purposes and are most powerful when you understand which one to reach for first. --- Xdebug: Callgrind Profiles for Deep Call-Tree Analysis ------------------------------------------------------ Xdebug's profiler writes Callgrind-format files that tools like QCacheGrind or KCacheGrind can visualise. It captures every function call with inclusive and exclusive cost, making it ideal for finding expensive recursive logic or unexpectedly deep call stacks. **Enable profiling for a single request** by triggering it with a query parameter rather than enabling it globally (which would kill throughput): ```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.%r ``` Then hit your endpoint with the trigger cookie or query string: ```bash curl "https://app.local/api/reports?XDEBUG_PROFILE=1" \ -H "Cookie: XDEBUG_PROFILE=1" ``` Open the resulting file in QCacheGrind. Sort by **Self Cost** to find functions that consume time independent of their callees — this surfaces things like a serializer being called 4,000 times inside a loop. ### What to Look For in Laravel - `Illuminate\Container\Container::make` appearing thousands of times signals you are resolving dependencies inside a loop instead of injecting them once. - `Illuminate\Database\Eloquent\Model::getAttribute` with high self cost often means you are accessing dynamic attributes in a tight loop — consider `toArray()` before iterating. - Blade's `__get` magic showing up heavily usually means a view is touching lazy-loaded relations. --- Blackfire: Timeline Profiling for Real-World Scenarios ------------------------------------------------------ Blackfire instruments PHP at the extension level with negligible overhead compared to Xdebug, making it safe to run against staging environments under realistic load. Its killer feature is the **timeline view**, which shows wall-clock time across I/O, SQL, cache, and HTTP calls in sequence. ```bash # Profile a single CLI command blackfire run php artisan import:products --limit=500 # Profile an HTTP request blackfire curl https://staging.app/api/dashboard ``` Blackfire's PHP SDK lets you add custom probes inside your code: ```php use Blackfire\Client; $blackfire = new Client(); $probe = $blackfire->createProbe(); // ... code under measurement ... $blackfire->endProbe($probe); ``` For Laravel, the more practical approach is the **Blackfire Player** for scripted scenarios: ```yaml # .blackfire.yaml scenarios: Dashboard load: - path: /api/dashboard headers: Authorization: "Bearer {{ env('BF_TOKEN') }}" assertions: - "metrics.sql.queries.count < 10" - "main.wall_time < 200ms" ``` These assertions fail your CI pipeline when a PR regresses query count or response time — a far more reliable guard than code review alone. --- Combining Both Tools: A Practical Workflow ------------------------------------------ 1. **Blackfire first** — run a timeline profile against the slow endpoint. Identify whether the bottleneck is SQL, PHP CPU, or external I/O. 2. **Xdebug second** — if Blackfire shows PHP CPU is the culprit, generate a Callgrind profile to find the exact function responsible. 3. **Fix, then assert** — add a Blackfire assertion to lock in the improvement. ### A Real Example: Slow Report Endpoint Blackfire timeline shows 47 SQL queries on `/reports/monthly`. The Xdebug callgrind reveals `Model::getAttribute` called inside `ReportLine::getFormattedAmountAttribute` which itself calls a currency conversion relation. The fix: ```php // Before: N+1 inside accessor public function getFormattedAmountAttribute(): string { return $this->currency->symbol . number_format($this->amount, 2); } // After: eager-load currency, compute in collection $lines = ReportLine::with('currency')->where('report_id', $id)->get(); $formatted = $lines->map(fn($l) => [ 'amount' => $l->currency->symbol . number_format($l->amount, 2), ]); ``` Queries drop from 47 to 2. The Blackfire assertion now enforces this permanently. --- Takeaways --------- - Use **Blackfire** for timeline profiling, CI assertions, and I/O-heavy scenarios where overhead matters. - Use **Xdebug callgrind** when Blackfire confirms CPU is the bottleneck and you need call-level granularity. - Never enable Xdebug profiling globally in any shared environment — use the trigger mechanism. - Blackfire's YAML assertions are the most underused feature: they turn profiling from a one-off task into a regression gate. - The most common Laravel bottlenecks found via profiling are container resolution in loops, lazy-loaded relations inside accessors, and Blade partials triggering repeated queries. Found this useful? [ ](https://twitter.com/intent/tweet?url=https%3A%2F%2Fwww.msaied.com%2Farticles%2Fprofiling-laravel-with-blackfire-and-xdebug-finding-real-bottlenecks-2&text=Profiling+Laravel+with+Blackfire+and+Xdebug%3A+Finding+Real+Bottlenecks) [ ](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fwww.msaied.com%2Farticles%2Fprofiling-laravel-with-blackfire-and-xdebug-finding-real-bottlenecks-2) Frequently Asked Questions ---------------------------- 3 questions Q01 Can I use Blackfire and Xdebug at the same time? No — both instruments PHP at the extension level and will conflict. Use Blackfire for timeline and overhead-sensitive profiling, then disable it and switch to Xdebug when you need deep call-tree analysis. Q02 Is it safe to run Blackfire on a staging server with real traffic? Blackfire's overhead is low enough for staging use, especially when triggered per-request via the browser extension or CLI. Avoid running continuous profiling under load; use it for targeted request sampling instead. Q03 How do I add Blackfire assertions to a Laravel CI pipeline? Add a `.blackfire.yaml` file to your repo with scenario paths and metric assertions. Run `blackfire player .blackfire.yaml` in your CI step. The command exits non-zero if any assertion fails, blocking the merge. Continue reading More Articles --------------- [ View all ](https://www.msaied.com/articles) [ ![Filament v5 Preview: What Is Changing and How to Prepare Your Codebase](https://cdn.msaied.com/711/0f685151a6c04b1c707230164839d12e.png) filament laravel filament-v5 ### Filament v5 Preview: What Is Changing and How to Prepare Your Codebase Filament v5 is on the horizon with deeper PHP 8.3+ type safety, a revised plugin contract, and schema composit... ![Mohamed Said](https://cdn.msaied.com/01M22N44A70A5MC2S599JP0MPH.webp) Mohamed Said 28 Sep 2026 4 min read Read ](https://www.msaied.com/articles/filament-v5-preview-what-is-changing-and-how-to-prepare-your-codebase-1) [ ![Tashil: Add Subscription Plans and Feature Usage Limits to Laravel](https://cdn.msaied.com/713/98c40d9d0472588d25d8b8359a96d1b1.png) Laravel Subscriptions SaaS ### Tashil: Add Subscription Plans and Feature Usage Limits to Laravel Tashil is a Laravel package that stores subscription plans in your database, tracks per-feature usage limits,... ![Mohamed Said](https://cdn.msaied.com/01M22N44A70A5MC2S599JP0MPH.webp) Mohamed Said 28 Sep 2026 4 min read Read ](https://www.msaied.com/articles/tashil-add-subscription-plans-and-feature-usage-limits-to-laravel) [ ![Laravel API Resources: Sparse Fieldsets, Conditional Relationships, and Cursor Pagination](https://cdn.msaied.com/710/4f310773d50e6b3a7ab53e64d3e76921.png) laravel api eloquent ### Laravel API Resources: Sparse Fieldsets, Conditional Relationships, and Cursor Pagination Go beyond basic JsonResource usage. Learn how to implement sparse fieldsets, conditionally load relationships... ![Mohamed Said](https://cdn.msaied.com/01M22N44A70A5MC2S599JP0MPH.webp) Mohamed Said 27 Sep 2026 3 min read Read ](https://www.msaied.com/articles/laravel-api-resources-sparse-fieldsets-conditional-relationships-and-cursor-pagination) [ ![Mohamed Said](https://cdn.msaied.com/01KT78WE565VEMM3PSNQAAB0MH.png) Mohamed Said Laravel Backend Engineer ](https://www.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://www.msaied.com) - [Projects](https://www.msaied.com/projects) - [Articles](https://www.msaied.com/articles) - [Certificates](https://www.msaied.com/certificates) - [Contact](https://www.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)