Chapters

37 Chapters | 3:44:49 |

01

Performance, Profilers and APMs

5:35
02

Blackfire Install: Agent, Probe, Chrome Extension

3:14
03

Installing the Agent, Probe & Chrome Extension

6:26
04

Wall Time, Exclusive Time & Other Wonders

7:47
05

Finding Issues via the Call Graph

6:50
06

Comparisons: Validate Performance Changes, Find Side Effects

3:56
07

Recommendations

6:25
08

Property Caching

8:17
09

Using a Caching Layer & Proving its Worth

4:24
10

The N+1 Problem & EXTRA_LAZY

5:59
11

Fixing N+1 With a Join?

4:38
12

Profile All Requests (Including Ajax)

6:03
13

The Blackfire CLI Tool for AJAX Requests

4:46
14

Profiling Command Line scripts

6:33
15

Timeline: Go Behind-the-Scenes with your Code

7:15
16

Timeline: Finding a Hidden Surprise

4:38
17

Spotting Heavy Object Instantiation

6:06
18

Service Subscribers

6:22
19

Manually Profile (Instrument) Part of your Code

9:04
20

SDK: Automatically Create a Profile

4:43
21

Creating an Automatic Probe Early in your Code

7:57
22

Performance Tests

6:45
23

All about Metrics

9:27
24

Assertions / Profile "Tests"

4:07
25

Blackfire Player

4:47
26

Expectations/Tests with Blackfire Player

6:10
27

Deploying to SymfonyCloud

5:01
28

Database Tricks on SymfonyCloud

8:00
29

Blackfire Environments

7:17
30

Production Profile: Cache Stats & More Recommendations

4:18
31

Automatic Performance Checks: Builds

7:15
32

Builds with Custom Scenarios

5:32
33

Per-Page Time Metrics & Custom Metrics

4:29
34

Testing a Build Compared to the Last Build

7:46
35

Staging Servers on SymfonyCloud

4:46
36

Staging Environment Builds

7:56
37

Blackfire Environment Variables

4:15

> Dev Tools > Blackfire.io: Revealing Performance Secrets with Profiling

06.

Comparisons: Validate Performance Changes, Find Side Effects

Autoplay

We've just updated our code to make a COUNT query instead of querying for all the comments for a user... just to count them. So, the page will definitely be faster. Right? Are you absolutely sure? Well, I think it will be faster... but sometimes making one part of your code faster... will make other parts slower. Fortunately, Blackfire has a special way to prove that a performance tweak does in fact help.

Let's profile the page now - I'll refresh... then click to profile. Give it a name to stay organized [Recording] Show page after count query.

Ok! Let's go see the call graph! https://bit.ly/sfcast-bf-profile2

Hey! 270 milliseconds total time - the last one was 415. So it is faster. We win! Tutorial over!

Well... yeah, I agree: it does look faster. But an important aspect of optimization is understanding why something is faster. Like, did this reduce CPU time? I/O wait time? And, maybe more importantly, did this change cause anything to be worse? For example, a change might decrease CPU time, but increase memory. If that happened, would the change really be a good one? It depends.

Comparing Profiles

This leads me to one of my favorite tools from Blackfire: the ability to compare profiles. Click back to your dashboard: the top two profiles are from the initial profile and then the page after using the COUNT query. On the right, hover over the "Compare" button on the original, click, then click the new one.

Say hello to the comparison view: https://bit.ly/sf-bf-compare1-2. Everything that's faster, or "better" is in blue. Anything that's slower or worse will be in red. And yea, it looks like the new profile is better in every single category. Ok, the I/O wait is higher - but .1 millisecond higher - that's just "noise".

Anyways, the comparison proves that this was a good change. Really, it's a huge win! On the call graph, in the darkest blue, the critical path this time is the path that improved the most. Click the UnitOfWork call now. Wow. The inclusive time is down by 90 milliseconds and even the memory plummeted: down 1.39 megabytes.

Tip

The SQL Query information requires a Profiler plan or higher.

But wait. One of the items on top is called "SQL Queries". The total query time is less than before... but we've added 5 more queries. We removed these 18 queries... but added 23 new ones.

Is that a problem? Probably not. Overall, this change was good. And if having too many queries does create a real problem - not just an imaginary one of "too many queries" - Blackfire will help us discover that. The big takeaway here is: don't just assume that a performance enhancement... is actually better. We'll see this later - not every change we'll do in this tutorial will prove to be a good one.

Next: Blackfire has a deep understanding of PHP, database queries, Redis calls and even libraries like Symfony, Doctrine, Magento, Composer, eZ platform, Wordpress and others. Thanks to that, it automatically detects problems and recommends solutions.

4 Comments

Sort By

alireza 3 years ago

Hi there, I just see two option in my toolbar, I don't see any queries or IO icon in toolbar, any idea?

| Reply |

MolloKhan SFCASTS alireza 3 years ago edited

Hey alireza

Sadly, those are paid features

Cheers!

1 | Reply |

alireza MolloKhan 3 years ago

What the heck? this is so sad.

| Reply |

MolloKhan SFCASTS alireza 3 years ago

Yeah, I got the same feeling. Blackfire is an awesome tool but you have to get a subscription to have access to the most useful features. But, if you have a successful application I think the price is good to pay for it

| Reply |

This tutorial can be used to learn how to profile any app - including Symfony 5.

Symfony 4

What PHP libraries does this tutorial use?

// composer.json
{
    "require": {
        "php": "^7.1.3",
        "ext-ctype": "*",
        "ext-iconv": "*",
        "blackfire/php-sdk": "^1.20", // v1.20.0
        "composer/package-versions-deprecated": "^1.11", // 1.11.99
        "doctrine/annotations": "^1.0", // v1.8.0
        "doctrine/doctrine-bundle": "^1.6.10|^2.0", // 1.11.2
        "doctrine/doctrine-migrations-bundle": "^1.3|^2.0", // v2.0.0
        "doctrine/orm": "^2.5.11", // v2.6.4
        "phpdocumentor/reflection-docblock": "^3.0|^4.0", // 4.3.2
        "sensio/framework-extra-bundle": "^5.4", // v5.5.1
        "symfony/console": "4.3.*", // v4.3.10
        "symfony/dotenv": "4.3.*", // v4.3.10
        "symfony/flex": "^1.9", // v1.21.6
        "symfony/form": "4.3.*", // v4.3.10
        "symfony/framework-bundle": "4.3.*", // v4.3.9
        "symfony/http-client": "4.3.*", // v4.3.10
        "symfony/property-access": "4.3.*", // v4.3.10
        "symfony/property-info": "4.3.*", // v4.3.10
        "symfony/security-bundle": "4.3.*", // v4.3.10
        "symfony/serializer": "4.3.*", // v4.3.10
        "symfony/twig-bundle": "4.3.*", // v4.3.10
        "symfony/validator": "4.3.*", // v4.3.10
        "symfony/webpack-encore-bundle": "^1.6", // v1.7.2
        "symfony/yaml": "4.3.*", // v4.3.10
        "twig/extensions": "^1.5" // v1.5.4
    },
    "require-dev": {
        "doctrine/doctrine-fixtures-bundle": "^3.2", // 3.2.2
        "easycorp/easy-log-handler": "^1.0.7", // v1.0.9
        "fzaninotto/faker": "^1.8", // v1.8.0
        "symfony/browser-kit": "4.3.*", // v4.3.10
        "symfony/css-selector": "4.3.*", // v4.3.10
        "symfony/debug-bundle": "4.3.*", // v4.3.10
        "symfony/maker-bundle": "^1.13", // v1.14.3
        "symfony/monolog-bundle": "^3.0", // v3.5.0
        "symfony/phpunit-bridge": "^5.0", // v5.0.3
        "symfony/stopwatch": "4.3.*", // v4.3.10
        "symfony/var-dumper": "4.3.*", // v4.3.10
        "symfony/web-profiler-bundle": "4.3.*" // v4.3.10
    }
}

Previous Chapter

Next Chapter

Comparisons: Validate Performance Changes, Find Side Effects

Share this awesome video!

Comparing Profiles

4 Comments

Delete comment?

What PHP libraries does this tutorial use?