I was looking over the profiling issue and the numbers look awesome. I'm working with several sites based on panels and always look for ways to increase performance. So what I'm trying to figure out is the best way to use this module with panel / panelized content types.

Would we need to get into the field level caching to make it effective with Panels? Or would it be sufficient to handle caching at the content type even if we're dropping fields into different panel regions?

As for views... I've always built field-level views given the history / recommendations elsewhere that building views with fields as opposed to node-based (e.g. teasers) was more efficient / performed better. I'm guessing that with this module we could build out node based views and choose a view mode and gain from this module?

Comments

Caseledde’s picture

Caseledde commented

Hi,

you earn the best performance if you use full cache only and don't render Fields. With Display Suite or Entity view modes you can configure several view modes to display different fields. Those view modes are fully cacheable.

The Field Cache level should only be used, if you have dynamic data within your view modes, like Fivestar or Flag.

I dont have much expirience with Display Cache combined with panelized content, but it should work the same.

Regarding views: Yes. If you refactor your views to use view modes instead of fields, you should gain a much better performance. In addition you should use the module Entity API and choose the build mode 'rendered entity' instead of, for example, 'rendered node'. This way you avoid the build of an renderer array and consequently time to render. Same way for Panels.

kars-t’s picture

kars-t commented
Status: Active » Fixed

As there where no more questions I believe this issue can be closed.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.