BO extremely slow

[costelc]

I had a 1.6.0 Prestashop with a custom theme which was working very nice. A couple of weeks ago the Backoffice started working extremely slow, each page load taking many minutes. There was no change or update done to Prestashop, and hosting says nothing changed on the server/configuration either.

 

I've upgraded Prestashop now to latest 1.6.1 but things are exactly the same. I've activated debug and profile, and BO just redirects now to profiling info, and the numbers there are huge: http://prntscr.com/b6g0fp

 

Frontend works good and fast, only backoffice is problematic.

 

Can you point me into the next step I should take trying to find the cause of this? How can I further investigate that "hookbackofficeheader" ?

[costelc]

All pages

[El Patron]

back office-->advanced parameters-->performance (see debug mode)

 

Let's think that your slowness issue is result of 3rd party module, so set to 'yet' these two debug settings

http://screencast.com/t/nD4rjjJj

 

If the slowness disappears then it's a module causing the problem, which one we do not know.  If BO is much faster then set you will need to disable each 3rd party moduley one by one until you can discover which is causing issue.

 

TIP: if disabled 3rd party modules/overrides seems to fix slowness,  and to determine what modules have been added recently, using FTP look at modules folder and  sort on 'date'.  This will give you idea of what has been loaded recently.

 

Best of luck, el

Edited May 21, 2016 by El Patron (see edit history)

[costelc]

After days of hair pulling I finally solved the problem. The culprit was the PAYU module, an old/outdated payment module that was not enabled or used. Detail of the plugin, in case anyone stumbles upon this issue:

 

Payments and Gateways

PayU v2.1.8 - by PayU

Accepts payments by PayU

 

What is completely shocking is that the module was disabled, and even with Advanced Parameters - Debug - Disable non Prestashop modules & Disable all overrides set to YES the problem was still present. So a module still has some active pieces of code (update maybe?) active even when disabled?

 

Only after uninstalling the problem went away and everything's back to normal.