Debug Mode. Questions on Hook Processing Size & time

[ricky11]

I am trying to understand Hook Processing Size & time when you enable debug mode in prestashop.

 

Attached file you can see the hook processing size and time.

 

I am confused as to why display top and display head are 8 and 12 mb?

 

I have uninstalled so many modules that i don't need. I have now 29 modules in displayheader.

 

Question, why is it in the displayheader do i need modiules such as cart block, ... as cartblock also appears in displaytop? is i duplicated?

 

Does displayhead mean only the home page or all pages?

 

thanks.

 

 

     

[ricky11]

Here is the link, I had posted another question about database queries, if the moderator finds these similar, he may delete one of them.

link removed.

Edited October 6, 2014 by ricky11 (see edit history)

[fransjaeger]

Following this

[thepan]

Hey

I asked myself the same before. All I can say is, that nearly all modules hook into "displayHeader" to insert some css code into the page.

[El Patron]

Hey

I asked myself the same before. All I can say is, that nearly all modules hook into "displayHeader" to insert some css code into the page.

 

this is correct answer for displayHeader, .css and .js are hooked here..

 

the long run time (for this page) is intiContent.  This is where 'bulk' of work is done by modules.

 

there is much more info than what you provided...so on mb on db (short ms time)...you would need to do more analysis.

[ricky11]

Thanks.... there is a tremendous amount of back end server work to get the store to display in under 2 seconds, even on a good VPS.

 

I have decided not to display any products on the home page in order to speed up the display time, so there should be almost zero database queries unless the user is logged in.

 

We should be focusing more on the core of front end development rather than the back end. If you look at other Ecommerce options like shopify or bigcommerce you can load 50 products on the page page and get it to load under 1 second.

 

Sure i can buy modules and modules and modules to speed it up, but that is not a solution.... Prestashop speed is now holding a lot of us back. I dont like worrying about backend server, spending too much time on it, and i am quite experienced.  I am using default theme with default database, but it still seems i need to optimize php queries.. i.e. work that prestashop should have done.

 

they finally deferred loading of JS in 1.6, but there is still a lot more work to do.