- Issue created by @geek-merlin
- last update
over 1 year ago Custom Commands Failed - @geek-merlin opened merge request.
- last update
over 1 year ago Custom Commands Failed - Status changed to Needs review
over 1 year ago 8:07pm 7 May 2023 - 🇩🇪Germany geek-merlin Freiburg, Germany
Some POC code to discuss the direction this goes.
- Status changed to Needs work
over 1 year ago 7:24pm 8 May 2023 - 🇨🇭Switzerland berdir Switzerland
I don't really understand the goal of this. Some real use cases of when you'd want to use this could help,
The example is technically valid, but it's not something you ever want to do. Ending up with too many node:list cache tags on your site is one of the main performance issues.
Invalidation and checking also doesn't follow the same rules. Going with the example, When invalidating, we typically invalidate node:ID, node:list, node:list_article and possibly more. And we must invalidate all of them. When checking for invalidation, I could imagine a case where we say if an item has node:list and node:ID then we can ignore node:ID, but with the bundle cache tags, that gets complicated/expensive again.
Maybe a scenario where you have 10 global config cache tags that all add some stuff to global attachments (like google analytics and others), those you could aggregate to a single one, but that will be very site specific and you'd need to hardcode that, because any sort of configuration for that will most likely be more expensive to check than an extra query or even just a more entries in an IN condition.
