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

Buy Access to Course

09.

Using a Caching Layer & Proving its Worth

|

Autoplay

Previous Chapter

Next Chapter

Login or register to check out the script

3 Comments

Sort By

Login or Register to join the conversation

Kiuega 5 years ago

Hi team! I love this way of caching items! In the video you set up a cache on the user_activity_text, referenced by the user ID. You invalidate this cache after 3600 seconds.

Couldn't we instead create a Doctrine listener, which, when a user adds / deletes a comment, then we invalidate the 'user_activity_text' cache referenced by that user?

In general, would managing the timeout manually using Doctrine listeners be a good solution?

I also appreciate the fact that you put forward the fact of creating a cache key per user, I was wondering if this was relevant or if we should have a cache for all users!

|

MolloKhan SFCASTS Kiuega 5 years ago edited

Hey Kiuega

Those are great questions. I think you can implement that listener and do what you say, it should work but you must be aware that Doctrine's listeners are not triggered when you run a custom query, i.e. when you don't create your query via the QueryBuilder. Another thing to consider is code clarity. It may not be obvious for other developers on your team how the cache it's cleared out. Perhaps you would prefer to manually clear the cache directly on the remove/add comment endpoints.

Cheers!

1 |

Kiuega MolloKhan 5 years ago

Thank you very much for your response and these tips! I will apply them for my project! :)

|

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