Is it Godaddy or me?

[InnovatecInc]

Hi there

 

loving Prestashop, not enjoying GoDaddy.

 

Our site has intermittent speed issues - sometimes the site is fast, other times incredibly slow - sometimes about 40 seconds to load the main page!!!!

 

I have tried to debug our store - turned off modules, overrides, smart caching etc - but still the same issues.

 

I called them - they ran a quick check on the server and said that the issue would most likely be at our end.

 

Any ideas would be most appreciated. I am sure it is Daddy not me!

 

Steve

Edited March 24, 2015 by InnovatecInc (see edit history)

[tuk66]

GoDaddy, or not GoDaddy, that is the question.

 

I think we can't narrow our choice to a provider. Every provider offers many options and have many servers. Overloaded as well as fast and worse, it is a moving target.

 

I would look for a good and stable reputation and deal with experience of other.

[InnovatecInc]

Thanks Tuk

 

I would assume that if I am accessing exactly the same product page and the time to load the info varies between 1 second and 40 second then this is a server issue NOT a

Prestashop issue - which is what GoDaddy support are suggesting . Below are some debug stats. Do they look ok? Sorry not the most tech savvy.

 

I have looked at the GA stats and we don't tend to have more then 2 concurrent users and our server resources are "one below" a GoDaddy "dedicated" server.

 

I really need to take the argument back to GoDaddy to see if they will investigate the issue further or move our store to a better server

 

Here is our site:

 

http://modernfurniture.com.au

 

Please any insight from anyone would be great!

 

Steve

 

 

 

Load time: 1438 ms
You'd better run your shop on a toaster

Execution Load time (ms) config 196 constructor 0 init 64 checkAccess 0 setMedia 2 postProcess 0 initHeader 0 initContent 1126 initFooter 43 display 7

Hook processing: 1171 ms / 19.37 Mb
48 methods called in 30 modules

Hook Processing displayHome 11.35 Mb in 1061ms displayHeader 5.89 Mb in 48 ms displayFooter 1.06 Mb in 43 ms displayTop 0.96 Mb in 15 ms displayNav 0.07 Mb in 2 ms displayHomeTabContent 0.03 Mb in 2 ms moduleRoutes - Mb in 0 ms actionDispatcher - Mb in 0 ms actionFrontControllerSetMedia - Mb in 0 ms displayHomeTab - Mb in 0 ms DisplayOverrideTemplate - Mb in 0 ms displayBanner - Mb in 0 ms

Memory peak usage: 28.0 Mb

Execution Memory (Mb) Total (Mb) config 5.25 5.4 constructor - 5.4 init 2.74 8.1 checkAccess - 8.1 setMedia 0.08 8.1 postProcess - 8.1 initHeader - 8.1 initContent 18.26 26.6 initFooter 1.08 27.5 display 0.29 28.0

Total cache size in Cache class: - Mb

Smarty cache: enabled

Smarty compilation: auto

SQL Queries: 485 queries in 1040 ms

Included files: 177 (3.36 Mb)

Global vars : 0.53 Mb

• $_MODULES ≈ 247k
• $_LANG ≈ 197k
• $context ≈ 67k
• $_ENV ≈ 10k
• $_SERVER ≈ 10k
• $_MODULE ≈ 4k
• $_REQUEST ≈ 2k
• $_COOKIE ≈ 2k

[NemoPS]

Iif you want my honest opinion, stay away from goGranny...err... goDaddy

[InnovatecInc]

I was on the phone to GD yesterday and they ran server and database tests and then emailed me the query below and said that this is causing our intermittent latency issues.

What I don't understand is why the same query can be run at different times of the day - and mostly return the results in a second - and at other times (30% of the time) return results in 30-40 seconds.

Any insight would be most appreciated as I need to solve this issue urgently.



[Tue Mar 24 10:03:28 2015] Query killed - furniture : SELECT P.*, PRODUCT_SHOP.*, STOCK.OUT_OF_STOCK, IFNULL(STOCK.QUANTITY, 0) AS QUANTITY, MAX(PRODUCT_ATTRIBUTE_SHOP.ID_PRODUCT_ATTRIBUTE) ID_PRODUCT_ATTRIBUTE, MAX(PRODUCT_ATTRIBUTE_SHOP.MINIMAL_QUANTITY) AS PRODUCT_ATTRIBUTE_MINIMAL_QUANTITY, PL.`DESCRIPTION`, PL.`DESCRIPTION_SHORT`, PL.`AVAILABLE_NOW`,

[Tue Mar 24 10:03:37 2015] Query killed - furniture : SELECT P.*, PRODUCT_SHOP.*, STOCK.OUT_OF_STOCK, IFNULL(STOCK.QUANTITY, 0) AS QUANTITY, MAX(PRODUCT_ATTRIBUTE_SHOP.ID_PRODUCT_ATTRIBUTE) ID_PRODUCT_ATTRIBUTE, MAX(PRODUCT_ATTRIBUTE_SHOP.MINIMAL_QUANTITY) AS PRODUCT_ATTRIBUTE_MINIMAL_QUANTITY, PL.`DESCRIPTION`, PL.`DESCRIPTION_SHORT`, PL.`AVAILABLE_NOW`,

[Tue Mar 24 10:03:37 2015] Query killed - furniture : SELECT P.*, PRODUCT_SHOP.*, STOCK.OUT_OF_STOCK, IFNULL(STOCK.QUANTITY, 0) AS QUANTITY, MAX(PRODUCT_ATTRIBUTE_SHOP.ID_PRODUCT_ATTRIBUTE) ID_PRODUCT_ATTRIBUTE, MAX(PRODUCT_ATTRIBUTE_SHOP.MINIMAL_QUANTITY) AS PRODUCT_ATTRIBUTE_MINIMAL_QUANTITY, PL.`DESCRIPTION`, PL.`DESCRIPTION_SHORT`, PL.`AVAILABLE_NOW`,

[Tue Mar 24 10:04:53 2015] Query killed - furniture : SELECT P.*, PRODUCT_SHOP.*, STOCK.OUT_OF_STOCK, IFNULL(STOCK.QUANTITY, 0) AS QUANTITY, MAX(PRODUCT_ATTRIBUTE_SHOP.ID_PRODUCT_ATTRIBUTE) ID_PRODUCT_ATTRIBUTE, MAX(PRODUCT_ATTRIBUTE_SHOP.MINIMAL_QUANTITY) AS PRODUCT_ATTRIBUTE_MINIMAL_QUANTITY, PL.`DESCRIPTION`, PL.`DESCRIPTION_SHORT`, PL.`AVAILABLE_NOW`,

[moy2010]

As Nemo said, stay away from GoDaddy for prestashop...

[InnovatecInc]

Thanks Moy2010

 

I read your performance tip and they were great!!

 

I would not be so concerned about this whole GD/PS performance issue but our shop does not get huge concurrent traffic - maybe 2-3 very so often - and we have a lots of resources on it. 

 

I am more concerned that some of the SQL queries are causing the issues.

 

When I look at the debug logs - the same page can have a different number of queries depending on what time the page is loaded.

 

I just need some insight from someone as to how to debug this issue.

 

s