[TwigComponent][Perf] Remove component dumping from profiler to reduce memory usage

[alinceDev]

IMHO, the component dump is not necessary in the profiler as it can be quite verbose and memory-intensive. When detailed component inspection is needed, it's preferable to dump the component manually in the specific context where debugging is required.

#3066

[smnandre]

You can disable the twig component profiler if you do not need it

[alinceDev]

Yes, I know it is possible to disable the profiler with the option:

twig_component:
    profiler: false

However, this option disables the entire profiler. We only need to disable the dumped components section, because it's consuming lot of memory
Please see my PR:
#3066

[smnandre]

@alinceDev

So i checked on the project I work on and .... I'm not a big fan of this idea (but not against the idea of not storing the components ... but)

Multiple data are only visible here in the profiler... and basic scalar data is not something that would take that much memory (at all).

Could you maybe create a repository / share some code (or context) to understand what numver of components (or what amount of inner data) becomes a problem in dev for you ?

I'd rather we change profiling and remove an important feature of it only if we have a concrete example to base this choice on....

[alinceDev]

Hi @smnandre,

On the homepage of our application, we have many widgets (Twig components) and anonymous components.

1 - Case with Twig component profiler ON

As you can see, the total memory usage for all components is 276 MB.
Some components have many dependencies:

2 - Case with no component dumping (when I comment out the part that renders the dumped component)

3 - Case with Twig component profiler OFF

In my PR, I propose removing case 2, because for case 1, we need to set the PHP memory_limit to 512M (the initial value was 128M).

[smnandre]

As much I 100% understand your frustration... three different screen with different memory settings do not help setting a good vision here, to be fair :|

Just made a test with a component with lots of big dependencies and it had no impact, because they are not only reference... i'm wondering if that may be due to some of the properties (widgets, items) you have in your component ?

Also just to be sure, are you using the last version of TwigComponent ?

--

To move on, I can assure you this feature is really usefull, at least when using LiveComponent.

Instead of removing it, could we maybe add an option there ?