• Home
  • Get help
  • Ask a question
Last post 14 hours 11 min ago
Posts last week 141
Average response time last week 4 hours 42 min
All time posts 67824
All time tickets 10480
All time avg. posts per day 21

Helpdesk is open from Monday through Friday CET

Please create an (free) account to post any question in the support area.
Please check the development versions area. Look at the changelog, maybe your specific problem has been resolved already!
All tickets are private and they cannot be viewed by anyone. We have made public only a few tickets that we found helpful, after removing private information from them.

#7581 – performance and sh404

Posted in ‘sh404SEF’
This is a public ticket. Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.
Friday, 15 January 2021 13:42 UTC
Laurentfrom47

Hello,

I wonder if for a site that I am going to redo, am I going to use sh404, I think so, but I wonder if it would not make the system a little lighter to use everything natively?

Have you ever measured the impact of the component on the performance of a small site?

Thank you for that.

I would like to make it clear that I am not criticizing sh404 because I really like what it brings.

Friday, 15 January 2021 14:03 UTC
wb_weeblr

Hi

Measured, no, because that would not have any meaning, could not be used in any other configuration than the one tested. There are still some comments to be made:

1. There will be some overhead due to sh404SEF. Just like any extension used, or depending on which Joomla feature you use (how many modules, ACL or not, multilingual or not?...)

2. sh404SEF uses most resources when SEF URL are created, that is the 1st time anyone visit a page where a link exists. After that, for any other visit to that page, the URL is already build and entirely read straight from the database. On smaller site (what is small??), difference cannot be measured it's too small.

Reading pre-built URLs from the DB is extremely quick, sometimes even faster than the Joomla SEF way (not for joomla itself but for many extensions).

Seems weird but if you have a page with 10 links on it, then each time this page is displayed to someone:

- sh404SEF reads each link directly built from the database (or cache), no additional work needed. One DB query per URL.

- Joomla SEF/extension has to build those 10 links. To build each link, the extension may have to read one or more categories details, one or more item details, etc 10 times. 

3. Enabling simple caching will take this out of the equation: the largest number of URLs (usually in the menu) are already stored in the cached copy of the meny, whether you have sh404SEF makes no difference.

4. Where you want to think twice about using sh404SEF is for a site that has a lot of URLs on each page, and there are very often a lot of new URLs. For instance, I would not enable sh404SEF on a large forum. Each page of a forum has hundreds of URLs, and there are new posts very often.

That said, sh404SEF would not help the SEO of a forum either, except in case of extreme duplicate content.

All of this to say that I don't consider performance an issue here. Especially on a "small" site, the difference is too small to be measured and/or to have any effect. If caching is enabled, then there won't be any difference at all. Only be careful for forums, extensions with pages where there are hundreds of links on the same page.

Of course, usually, its image size, javascript and CSS size that cause the most perf issue ;)

Best regards

Yannick Gaultier

weeblr.com / @weeblr

 

 
Friday, 15 January 2021 14:07 UTC
Laurentfrom47

OK, thanks i understand.

Bon weekend en gironde ;)

 

Friday, 15 January 2021 14:56 UTC
wb_weeblr

Hi

Merci, de même!

Best regards

Yannick Gaultier

weeblr.com / @weeblr

 

 
This ticket is closed, therefore read-only. You can no longer reply to it. If you need to provide more information, please open a new ticket and mention this ticket's number.