We have exactly one valid use case for invalidating a specific item in core vs delete (CacheCollector), but I don't see a use case for invalidateAll(). There is \Drupal\system\Entity\Menu::save(), but IMHO, it's mostly a naming problem because you invalidate the cache. But really you should use deleteAll() in that case IMHO, which actually deletes the entries (in the database implementation. redis is another special thing).
Quite a lot of calls in contrib (https://git.drupalcode.org/search?group_id=2&scope=blobs&search=%22-%3Ei...), most of those are just flat out wrong (cache.render invalidate all should really invalidate the rendered cache tag, that won't work for page cache and dynamic page cache)
Reason: It's an expensive thing for redis and I guess also memcache to support, because redis implements it as an extra cache tag. See 📌 Optimize bin cache tags and last write timetamp Active as a related issue.
Active
11.0 🔥
cache system
It affects performance. It is often combined with the Needs profiling tag.
Created a basic merge request, will need an update with the change record if others agree.
Can we add a CR for the deprecations and update the messages to use that link vs the issue. Since there is a replacement I'm a big fan of before/after snippets
I tend to start off without to get early feedback. But I'm also aware that helps with explaining the reason, created one now.