WebsiteBaker Community Forum

WebsiteBaker Support (2.12.x) => General Help & Support => Topic started by: svsanchez on April 30, 2020, 01:53:47 AM

Title: Site SLOW after upgrade from 2.8.3 to 2.12.1
Post by: svsanchez on April 30, 2020, 01:53:47 AM
Hello, I'm having a strange problem with WB after upgrading from 2.8.3 to 2.12.1

The page is EXTREMELY SLOW: each time I click on a link to a page, it takes from 30 seconds up to 1 minute before it starts showing something. Before the upgrade, it took less than 5 seconds to display.

Here are some example URLs:


How do I correct this performance downgrade after the upgrade?
Title: Re: Site SLOW after upgrade from 2.8.3 to 2.12.1
Post by: svsanchez on April 30, 2020, 03:37:22 AM
Just an update: my host replied to me that there is no load on the server, no connections saturation in Apache, no Spam being sent, no MySQL abuse and the DNS zone for the domain is correct. In general, the server is working very stable. Additionally, they say there's nothing in the logs that indicate a problem.

They say that the slowliness is due to our CMS (WB) and they recommend to check it's configuration.


Title: Re: Site SLOW after upgrade from 2.8.3 to 2.12.1
Post by: hgs on April 30, 2020, 07:49:51 AM
Based on your starting post one more question of understanding.
https://forum.WebsiteBaker.org/index.php/topic,31730.msg222082.html#msg222082
Why only upgrade to WB 2.12.1? We have a bugfixed version WB 2.12.2 for a long time.
And which php version is in use there

A second question or suggestion:
Have you ever tried to test the upgrade as a subdomain on https://www.deguate.com?
for example as https://www.test.deguate.com

Title: Re: Site SLOW after upgrade from 2.8.3 to 2.12.1
Post by: dbs on April 30, 2020, 08:04:50 AM
You load "1000" external scripts. jQuery twice (the one from code.jquery.com you can delete).
You can try to load all javascripts at the end of body.
Can you deactivate your .htaccess for testing? Is the site faster then?

You could provide us a backup of your installation.
User "hgs" could make a subdomain and we can better test and search for problems.
Title: Re: Site SLOW after upgrade from 2.8.3 to 2.12.1
Post by: hgs on April 30, 2020, 08:19:06 AM
Yeah, that's one possibility.
Please download a ZIP archive from the website with WB 2.8.3 and the database dump of it.
If this is ok, send the access data to my FTP server via pm
Title: Re: Site SLOW after upgrade from 2.8.3 to 2.12.1
Post by: svsanchez on April 30, 2020, 09:30:01 AM
Hello hgs and dbs!

I have been making several tests and noticed that the worst performance occured after a MySQL 5.7 to Maria DB 10.3 upgrade. This is the case with the superpromos.info site. This site is currently using PHP 7.3, but I also tried 7.0, 7.1 and 7.2 which made no difference.

The performance of another test site which I upgraded to 2.12.1 wasn't as bad as the superpromos.info site, but still pages were taking from 7 to 10 seconds to respond. I removed that test site but will install it again and upgrade it to 2.12.2 as suggested. Tried this one with PHP 7.0, 7.1 and 7.2.

I reinstalled the main site WITHOUT upgrade (2.8.3) and this one is pretty fast even with the "1000" external javascripts. It responds in less than 2 secs and will try to make it faster by loading the "1000" external javascripts from the footer as suggested and will remove the code.jquery.com. This one is using PHP 5.6. I would like to upgrade this one but since it's so big I need a "modification" on the /admin/pages/index.php file so that when I click on the PLUS sign to expand a parent category, it opens the subcategories in a new page like Ruud did a few years ago (I opened a different thread for this).

It's 1h30 AM here and I've been doing all these tests today so I'm going to bed now, but I will definitely install the 2.12.2 and send you the ftp details.

FYI, this is what my host responded about the slow superpromos.info after I asked them about the MariaDB upgrade:

When visiting the site and monitoring resource usage the "mysql" process would instantly start utilizing 100% of one your server's CPU available CPU threads.
Once the query, or request to the site has finished or closed this process would go down just as quickly. This behavior did not seem to have an effect on the other sites or
processes on the server however and leads us to believe that this sit in particular needs to be adjusted in the queries it is making to its database as other sites on the server
are not showing similar signs or issues. It appears that part of the query to database is to continually gather all tables and count them for a specific search. This is likely
the cause of your issue however if this is the cause this would be an issue that would need to be changed at the site level with how the site is coded to make database queries.
Title: Re: Site SLOW after upgrade from 2.8.3 to 2.12.1
Post by: svsanchez on April 30, 2020, 09:40:58 AM
I'm sorry dbs, regarding what you said about removing the script from code.jquery.com, do you mean:

This one?

<?php
 register_frontend_m odfiles('css');
 register_frontend_m odfiles('jquery');
 register_frontend_m odfiles('js');
?>


Or this one?

<?php
   // automatically include optional WB module files (frontend.css, frontend.js)
   if (function_exists('register_frontend_m odfiles')) {
      register_frontend_m odfiles('css');
      // register_frontend_m odfiles('jquery');
      register_frontend_m odfiles('js');
   } ?>

Or another one (could find anything else that said jquery)

Thank you.
Title: Re: Site SLOW after upgrade from 2.8.3 to 2.12.1
Post by: dbs on April 30, 2020, 09:46:35 AM
Sleep well, here is 10h AM.  :)

Quote
I'm sorry dbs, regarding what you said about removing the script from code.jquery.com, do you mean:
This one?
I saw at the end of your head a <link href="https://code.jquery...

For the other problems:
Ok, seems it is a special problem if someone has many pages. The Devs can have also have a look if you provide access.
My plan was to test your installation on a different server, but it is better on your server.
How many pages you have?