I think it is valid issue.
However I do not see an easy way to fix it.
Currently we have cache stored per $option, and $key based on $app->registeredurlparams

That does not allow us to distinct the cache per Article, at least I do not see how.
Maybe someone have better knowledge about this part.

ok think about this. An article can be cached as

• A Single Article View
• A Blog Category Menu Item page
• A list of articles in a table list view
• etc

So flushing the cache of JUST the article is not going to be enough to clear your site of old cached versions. The whole com_content cache needs clearing.

The whole com_content cache needs clearing.

No it doesn't. Think about a site with 10.000 articles. Or 50.000 articles. Do you want to clear the whole cache every time you save 1 article? That defeats the purpose of cache in the first place.

According to what you've brought up, if someone is a smart developer, what should be said instead is:

• Clear article ID
• Clear category that the article belongs to

That's it

Joomla doesn't cache per article or per category. It caches views.

Joomla doesn't cache per article or per category. It caches views.

Well, and that's the purpose of this issue. Doing it that way with no tracking of IDs is clearly bad / unoptimized, since it causes the issue that I brought up in this OP.

Well, and that's the purpose of this issue. Doing it that way with no idea of IDs is clearly bad / unoptimized, since it causes the issue that I brought up in this OP.

So what you are requesting is a complete overhaul of the caching system that Joomla has used for a decade...

Joomla 4 will clear all these caches on saving an article. Gulp.

		parent::cleanCache('com_content');
		parent::cleanCache('mod_articles_archive');
		parent::cleanCache('mod_articles_categories');
		parent::cleanCache('mod_articles_category');
		parent::cleanCache('mod_articles_latest');
		parent::cleanCache('mod_articles_news');
		parent::cleanCache('mod_articles_popular');

So what you are requesting is a complete overhaul of the caching system that Joomla has used for a decade...

I had/have no idea of the underlying code. Just bringing up an issue. No idea how hard or easy it is to change.

Joomla 4 will clear all these caches on saving an article. Gulp.

Gulp indeed.

To be clear - Im not defending how it is, its clearly not optimised for continuous editing on a live site - you have identified that and many before you have. The large sites I manage all do caching architecturally (on a load balancer or redis backed store) before even getting to Joomla, on a page basis too.

But basically its a huge job to refactor the caching layer to stop caching per "page" and start caching based on the "object cache" (where content is just an object) - certainly nothing is going to change fast here.

Me too, I'm personally using Litespeed Cache with the LSCache plugin for Joomla (which is smart to only clear cache of changed objects when they change, instead of all objects)

Just looking out for the betterment of Joomla.

Caching single Article can be achieved if the cache stored per article <key> (eg id),
instead of cache/com_content/ could be cache/com_content/<key>/

However this will not help for a list views: blog, category etc. Here need to change the rendering to be per "Item" (instead of per "view"), and then we will be able to cache every item separately.

Do you guys think this could be improved for Joomla 4?

It always can be improved, but I cannot say if it happen in J4.
However the issue is valid, not a high priority but it is valid especially for a large sites that use caching.