- 🇺🇸United States SamLerner
I agree, I'd also like to know why we need a table to record how many invalidations a particular tag has. The cachetag table seems to grow endlessly, as pointed out in 📌 Cache tags grows endlessly Active
My project have more than 10 million of entities, that have persistent_cache = FALSE property. They are not added to cache_entity table and this is right.
But the problem is that Drupal still save invalidations statistics into cachetags table, as result my cachetags table filled up by millions of unnecessary records, that dramatically slow-down the whole Drupal cache performance.
1. Create the `test1` custom entity with persistent_cache = FALSE property.
2. Create about 1000 entities.
3. Lookup into cache_entity SQL table - you will not see those entities in it.
3. Lookup into cachetags SQL table - you will see 1000 records with tag like test1:123
Drupal should check the persistent_cache = FALSE and skip saving statistics to cachetags SQL table.
Active
11.0 🔥
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
I agree, I'd also like to know why we need a table to record how many invalidations a particular tag has. The cachetag table seems to grow endlessly, as pointed out in 📌 Cache tags grows endlessly Active