No Code Attached Yet Performance
avatar Stuartemk
Stuartemk
10 Jun 2020

Is your feature request related to a problem?

Assets in Joomla are a disaster because regardless of their origin, whether it is a publication or a plugin or a template or component or modules they are all together; What it happens that in sites with many publications (for example about 40,000 a year) as in a news page the reading of the assets leads to the ttfb ("Time To First Byte") going from a response time of 50ms to 3000ms for example. This explains why in a new, clean joomla installation the behavior is so fast and over time it becomes so slow as articles are added. So it is necessary to separate the system assets (plugins, templates, components and modules) and put the assets that originate the articles APART or possibly eliminate that the articles and categories NO longer generate assets.

Describe the solution you'd like

So it is necessary to separate the system assets (plugins, templates, components and modules) and put the assets that originate the articles APART or possibly eliminate that the articles and categories NO longer generate assets.

Additional context

avatar Stuartemk Stuartemk - open - 10 Jun 2020
avatar joomla-cms-bot joomla-cms-bot - change - 10 Jun 2020
Labels Added: ?
avatar joomla-cms-bot joomla-cms-bot - labeled - 10 Jun 2020
avatar Stuartemk
Stuartemk - comment - 7 Oct 2020
avatar Hackwar Hackwar - change - 20 Feb 2023
Labels Added: ? No Code Attached Yet
Removed: ?
avatar Hackwar Hackwar - labeled - 20 Feb 2023
avatar Hackwar Hackwar - change - 27 Nov 2024
Status New Closed
Closed_Date 0000-00-00 00:00:00 2024-11-27 11:39:45
Closed_By Hackwar
Labels Added: Feature
Removed: ?
avatar Hackwar Hackwar - close - 27 Nov 2024
avatar Hackwar
Hackwar - comment - 27 Nov 2024

I also looked at this issue for a long time and did both tests right now and in the past and I think you are barking up the wrong tree here. We aren't loading Gigabytes of data on each request from the assets table and even millions of rows in a table aren't a big issue for a RDBMS. Please get another professional opinion on the site in question and see which optimisations are possible there, but the assets table is also not really something which we will change. Because of that I'm closing this issue.

avatar Fedik
Fedik - comment - 27 Nov 2024

@Stuartemk @Hackwar there actualy a fix that can address this issue #44078
Please review and test.

avatar Fedik Fedik - change - 27 Nov 2024
Labels Added: Performance
Removed: Feature
avatar Fedik Fedik - labeled - 27 Nov 2024
avatar Fedik Fedik - unlabeled - 27 Nov 2024

Add a Comment

Login with GitHub to post a comment