Multiple Nested Parsys slowing down AEM/Browser?

[Tyler_Maynard]

We've chose a very atomic approach to our AEM development. Having the ability to create many of our front end needs through simple components that add up to create more complex components.

I have my page's main parsys. I then drag 'layout compontent' that includes a parsys, In that parsys I drag a hide-show component that has its own parsys, I then drag a two column component that has two parsys, one for each column, and finally a more content specific component that has some headings and an embedded RTE.

I have used all of these components multiple places, but never in such a nested form for the needs of a particular page. Up until now I haven't had any browser slowdown or antyhing like that.

This strange combination of components gives some serious lag time when saving dialogs, or loading the page. Basically anytime there is a re-draw of the page. At times I even get the 'Aww Snap' crash in chrome. I have tried other browsers and they seem to be slowed down as well.

Is there a limit/problem with this nested parsys approach?

[kautuk_sahni]

Hi 

Please have a look at this community article covering Implementation and limitation of nested Paragraph system :-

Link:- http://www.citytechinc.com/us/en/blog/2013/02/limitations_of_the_cq_parsys.html

Examples:- https://gist.github.com/kand/4999238

We need to make our designing in such a way that nested parsys should be avoided. We can play with Layout Container, CSS etc. But still if it is needed then the design must be optimized. If we would keep multi-level nesting then performance could be impacted, as resolution of them would occur in Stack pop fashion. To debug this, you can check the network tab of browser debugging tool or Adobe ACS tool :- http://adobe-consulting-services.github.io/acs-aem-tools/aem-chrome-plugin/

Thanks and Regards

Kautuk Sahni