Follow-up from 🐛 getViewBuilder('node')->viewMultiple() bypasses render cache Needs work see also the discussion there.
When rendering multiples of the same thing - say a list of ten nodes, we cache both the overall list and each individual node.
With a cold cache, there can be a benefit to multiple loading both the nodes themselves, and entities that are referenced - i.e. if each node view renders some author information, the author entities could be loaded together too.
Since render cache misses operate at the level of the individual rendered item - i.e. one node at a time rather than multiple, this isn't currently possible to do.
Theoretically it should be possible to cache get items at the same level of a render array, keep track of the cache misses, then run a callback on all the cache misses together. So if we have ten nodes, and eight are a cache miss, a callback gets a chance to operate on the eight misses (loading the nodes and any referenced entities in preparation for rendering).
Closed: outdated
11.0 🔥
render system
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
📌 Render the navigation toolbar in a placeholder Active is one part of this.
📌 Entity lazy multiple front loading Active is another.
🌱 [meta] Placeholder-driven performance improvements Active is yet another.
Given those three issues exist, closing this out.