Any tips on an optimisation approach?

[michaeljcoyne]

Looking at my debugbar. My page is taking 10s to load locally.

There are quite a few blocks just rendering out the data in blade.

Does anyone have any tips for optimisation?

I am starting with creating block classes and using Laravels cache. To try to speed up response time but would like to hear any other tips for Twill.

Thanks

[michaeljcoyne]

Even when I have blank Blade files it is still taking 6s which is slow.

[michaeljcoyne]

A solution that works is to do a custom HasBlocks trait and use caching if not in preview mode.

[ifox]

Hi @michaeljcoyne, there are a lot of things that could affect your local loading time.

As far as retrieving Twill data goes, optimization techniques are the same as Laravel's, like avoiding n+1 queries by leveraging eager-loading and/or introducing caching (config, routes, queries), etc...

I'd recommend using a package like Laravel Debug Bar to understand where that time is going.

[michaeljcoyne]

Hi @ifox The slowness was all Twills code.

As I say I have done a custom trait which caches the render blocks functionality and the speed is in milliseconds now.

I could tell this as I alreaddy have the debug bar.

Thanks

[ifox]

Can you please share what you are doing within those blocks? If you have a lot of them with a lot of browsers and all those records have medias, translations, slugs and so on, that could explain it. The caching layer you added is certainly great, but it doesn't solve the fact that when your cache is cold it will still take a while, so I'd recommend still looking into improving the underlying performance. If you can help us reproduce the issue, I would really appreciate it.

[michaeljcoyne]

Hi @ifox

Yes I use translations, medias, repeaters and fair few attributes. I need to for my site.

I will have to look into cache generation of related modules perhaps via a task which gets hit on the Model boot method (when it gets updated).

This should solve the problem of cold cache - but probably not the easiest task to write to find all related browser modules then regenerate the cache depending if it is on that page. But I think this is the approach I will take. Currently I am clearing the whole cache on the base model boot - which isn't ideal.

[ifox]

Of course, I'm not saying you should not use those functionalities! I'm trying however to understand at what scale you're using them.

[ifox]

How many blocks, how many repeater items in them, how many records selected in browser field, etc... Also what is 10s including? Is that TTFB? Or DOM ready?