- 🇬🇧United Kingdom catch
Render cache multiple get is now in core after 📌 Render the navigation toolbar in a placeholder Active , we should see if there's an example in core where this would help, and then try to implement it in the renderer.
#pre_render + #cache is great, but has one big disadvantage:
Items in listings (300 comments, 20 blocks) are gotten one item at a time.
That means 300 cache_get instead of one cache_get_multiple().
The previous block cache did a get_multiple per region and hence was faster.
Add a cache pre-fetching foreach () loop on all children to Renderer::render().
Possibly set the pre-warmed data on an internal #cache_data attribute temporarily and remove after the #cache check again.
- Write a patch
- None
- None, no API change at all. Pure performance optimization.
--
This is major because of the performance impact. It likely is also a pretty simple quick fix.
Active
11.0 🔥
cache system
It affects performance. It is often combined with the Needs profiling tag.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
Render cache multiple get is now in core after 📌 Render the navigation toolbar in a placeholder Active , we should see if there's an example in core where this would help, and then try to implement it in the renderer.