Priming cache.app

Hi ahmedbhs!

> What's the default value of query_cache_driver

It depends on your version of DoctrineBundle, but basically the short answer is that (if you have a recent version) then it will use the same driver as cache.system. Basically, it creates a new "pool" off of cache.system, which usually uses opcache internally, iirc.

> is it better/faster to set it to apcu or redis

It probably wouldn't make a difference :). The fact that you're caching will give you 99% of the overall boost available.

> By default, does doctrine set the result of repository queries under cache ?

No, it does not cache the *results* of the queries by default. You *can* do this, however. In modern versions of DoctrineBundle, this cache is enabled by default (it uses a pool off of cache.app). However, you need to activate it on a case-by-case basis, as caching query results may mean you need to think about invalidation etc. Specifically, it's the useResultCache(true) part - https://www.doctrine-projec... - I don't have any experience using this. I DO cache sometimes, but I usually will call a query in Doctrine, get the result, then cache whatever I need manually use Symfony's cache service.

Cheers!

Hey Cesar!

Interesting! So.... the answer depends on what you mean exactly by "some of my users are still watching the previous version". On a PHP level, during deploy, 100% of the users are still using the original PHP code path. After deploy, 100% of the users are using the NEW PHP code path (as soon as the symbolic link changes, all requests use the new code). However, if you're referring to JavaScript or CSS, then it's more interesting :). If you make an update to a JS or CSS file and deploy, the new JS or CSS file will be deployed just like any other file. However, the user's browser might still use the old, *cached* version.

Is this your issue? If so, you need to use a cache busting strategy. I *highly* recommend using Webpack Encore, as it will handle cache busting / versioning automatically. We're creating a screencast about this right now - https://knpuniversity.com/s... - but you can find details here: https://symfony.com/doc/cur...

Cheers!

Thanks Ryan for answering. That's exactly my issue with CSS and JS. I would like to buy your tutorial when it's complete. Do I need to watch first another tutorial before to enter in this one?. Also, meanwhile, do you recommend me to use ascetic or http-cache?

Hey Cesar,

Do you mean watching Webpack course before Webpack Encore? Actually Encore is just a simple wrapper around Webpack which makes your work with Webpack library drastically simpler. So, you can start directly with Encore course, but if you need to dive deeper into Webpack - you need the Webpack course. However, I'd recommend to see Webpack course to understand Webpack and Webpack Encore better.

If you mean AsseticBundle - Webpack Encore is the tool which completely replaces this bundle and adds you more more features out of the box. So if you're going to use Encore - forget about AsseticBundle at all.

About HTTP cache: it depends on your project, if you have a simple website with a lot of public content (not user-specific pages or user-specific blocks on each page) - it makes sense. Otherwise it could be even overhead in some cases. Anyway, HTTP cache complicates things a lot and you need to start thinking about cache invalidation on deploys. I'd recommend you to look at Symfony Cache Component first that are enough in most cases and that is much simpler.

Cheers!

Thanks Victor. When are you calculating to finish the Webpack Encore course? I am going to buy it or sure.

Yo Cesar,

Webpack Encore is going to be completely released in a few weeks, as you might notice we're working on it right now and trying to release a new video every day. And Webpack Encore course will be FREE for everyone! But if you're looking for buying something, take a look at paid Webpack course which is already completely released :p

Cheers!