jrelectronix Posted October 13, 2014 Share Posted October 13, 2014 Hi everyone, I have a problem with my Back Office; it's very slow and this happened suddenly. Frontoffice is working well, so I don't know what's wrong in the backoffice. Here is the debug mode data: Load time: 46.585sYou'd better run your shop on a toasterconfig: 84ms constructor: 0ms init: 52ms checkAccess: 0ms setMedia: 8ms postProcess: 0ms initHeader: 11ms initContent: 46.422s initFooter: 0ms display: 8ms Hook processing: 29ms / 3.64 Mb4 methods called in 4 modulesdisplayBackOfficeHeader: 25ms / 3.06 Mb actionAdminControllerSetMedia: 4ms / 0.57 Mb moduleRoutes: 0ms / 0 Mb displayBackOfficeFooter: 0ms / 0 Mb displayBackOfficeTop: 0ms / 0 Mb actionDispatcher: 0ms / 0 Mb Memory peak usage: 49.5 Mbconfig: 12.2 Mb (12.2 Mb) constructor: 0 Mb (12.2 Mb) init: 5.05 Mb (17.4 Mb) checkAccess: 0 Mb (17.4 Mb) setMedia: 0.89 Mb (18.6 Mb) postProcess: 0 Mb (18.6 Mb) initHeader: 0.78 Mb (19.1 Mb) initContent: 29.58 Mb (48.9 Mb) initFooter: 0.01 Mb (48.9 Mb) display: 0.58 Mb (49.5 Mb) Total cache size (in Cache class): 0.39 Mb DB type: DbPDO SQL Queries: 57 queries Time spent querying: 56ms Included files: 322Size of included files: 4.21 Mb Globals (> 1 Ko only): 2049 Ko_LANGADM ≈ 1199 Ko _MODULES ≈ 806.2 Ko HTTP_SERVER_VARS ≈ 7.9 Ko _SERVER ≈ 7.9 Ko _ENV ≈ 6.9 Ko HTTP_ENV_VARS ≈ 6.9 Ko _MODULE ≈ 4.3 Ko _REQUEST ≈ 2.2 Ko _GET ≈ 1.4 Ko HTTP_COOKIE_VARS ≈ 1.3 Ko _COOKIE ≈ 1.3 Ko HTTP_GET_VARS ≈ 1.2 Ko Link to comment Share on other sites More sharing options...
musicmaster Posted October 14, 2014 Share Posted October 14, 2014 In the file defines.inc.php you can switch sql profiling on ('_PS_DEBUG_PROFILING_'). That will enable you to see which query takes so long. Link to comment Share on other sites More sharing options...
PrestaHeroes USA Posted October 14, 2014 Share Posted October 14, 2014 these are harder to debug because the delay is in initcontent but we don't see any hook process taking any amount of time. even the sql is is zipping along. in other words I don't see related 'long time' in other parts of that report that can relate to initcontent. I'd think 'real hard' what did I change? i.e. did you load a module lately? If you can't remember loading a module for example, use ftp to look at modules folder, and look at file dates. also make sure to turn on error reporting to see if there is a time out issue. plug for my sort of famous module bozoom. 1 Link to comment Share on other sites More sharing options...
jrelectronix Posted October 14, 2014 Author Share Posted October 14, 2014 these are harder to debug because the delay is in initcontent but we don't see any hook process taking any amount of time. even the sql is is zipping along. in other words I don't see related 'long time' in other parts of that report that can relate to initcontent. I'd think 'real hard' what did I change? i.e. did you load a module lately? If you can't remember loading a module for example, use ftp to look at modules folder, and look at file dates. also make sure to turn on error reporting to see if there is a time out issue. plug for my sort of famous module bozoom. Thanks El Patron, I'm gonna check the dates if there was any update, or so. Link to comment Share on other sites More sharing options...
PrestaHeroes USA Posted October 14, 2014 Share Posted October 14, 2014 and make sure to enable deug mode http://www.prestashop.com/forums/topic/224525-how-to-turn-on-error-reporting-for-debug-information/ because there may be some good info like timeout error, hopefully something more useful to help debug Link to comment Share on other sites More sharing options...
Pieter Posted March 26, 2015 Share Posted March 26, 2015 (edited) Hi, was experiencing same problem especially time on hook DisplayBackOfficeHeader was huge. made visible with define('_PS_DEBUG_PROFILING_', true); setting in config/defines.inc.php. Found a solution on the german forum: get rid of module Cron Taskmanager Worked like a charm! Loading time now under 500ms ! Edited March 26, 2015 by Pieter (see edit history) 2 Link to comment Share on other sites More sharing options...
ccw0103 Posted June 2, 2015 Share Posted June 2, 2015 I wan to thank @Pieter for suggesting "get rid of module Cron Taskmanager" <---this solved my problem too....but is this something prestashop developing team should looking into??? Link to comment Share on other sites More sharing options...
bakko88 Posted February 20, 2016 Share Posted February 20, 2016 Hi, was experiencing same problem especially time on hook DisplayBackOfficeHeader was huge. made visible with define('_PS_DEBUG_PROFILING_', true); setting in config/defines.inc.php. Found a solution on the german forum: get rid of module Cron Taskmanager Worked like a charm! Loading time now under 500ms ! I wan to thank @Pieter for suggesting "get rid of module Cron Taskmanager" <---this solved my problem too....but is this something prestashop developing team should looking into??? Hi guys , can u tell me how do u found it? I don t find in google Link to comment Share on other sites More sharing options...
pzn66 Posted May 13, 2016 Share Posted May 13, 2016 hi, I have the same problem. I have almost read all of the posts and checked the file permission also checked the performance configuration and firewall setting. but the BO is too slow after all. and the debug says: oad time: 63292 msYou'd better run your shop on a toaster Execution Load time (ms) config 235 constructor 0 init 63022 checkAccess 0 setMedia 0 postProcess 0 initHeader 0 initContent 29 initFooter 0 display 6 ook processing: 63030 ms / 1.31 Mb2 methods called in 2 modules Hook Processing displayBackOfficeTop 0.42 Mb in 63016ms moduleRoutes 0.89 Mb in 13 ms actionAdminLoginOptionsModifier 0.00 Mb in 0 ms actionDispatcher 0.00 Mb in 0 ms what is the problem with displayBackOfficeTop ? please help me. thanks. Link to comment Share on other sites More sharing options...
vekia Posted May 14, 2016 Share Posted May 14, 2016 hi, I have the same problem. I have almost read all of the posts and checked the file permission also checked the performance configuration and firewall setting. but the BO is too slow after all. and the debug says: oad time: 63292 msYou'd better run your shop on a toaster Execution Load time (ms) config 235 constructor 0 init 63022 checkAccess 0 setMedia 0 postProcess 0 initHeader 0 initContent 29 initFooter 0 display 6 ook processing: 63030 ms / 1.31 Mb2 methods called in 2 modules Hook Processing displayBackOfficeTop 0.42 Mb in 63016ms moduleRoutes 0.89 Mb in 13 ms actionAdminLoginOptionsModifier 0.00 Mb in 0 ms actionDispatcher0.00 Mb in 0 ms what is the problem with displayBackOfficeTop ? please help me. thanks. have you tried method with disabling (even removing) cron taskmanager module? Link to comment Share on other sites More sharing options...
pzn66 Posted May 15, 2016 Share Posted May 15, 2016 yes first I disabled cron taskmanager module and after that I removed it, but the problem remains, the BO is too slow. Link to comment Share on other sites More sharing options...
PrestaHeroes USA Posted May 15, 2016 Share Posted May 15, 2016 yes first I disabled cron taskmanager module and after that I removed it, but the problem remains, the BO is too slow. please attach screen shot of following: back office-->advanced parms-->configuration information back office-->advanced parms-->performance Provide link to your hosting plan description.... also: test this: back office-->advanced parms-->performance-->debug-->disable 3rd party modules and overrides, then retest. This tells us if you have 3rd party module causing issue or not. Do all that then report back. Link to comment Share on other sites More sharing options...
pzn66 Posted May 15, 2016 Share Posted May 15, 2016 thank you for your reply. I did what you said. I have uploaded screen shots : http://uploads.im/?g=k1Vl7.jpg And I do what you said, YES! When I disabled 3rd party modules, every thing works fine! it seems that there is a problem with my theme, because the FO layout and links and menus do not work now. what should I do now ? Link to comment Share on other sites More sharing options...
pzn66 Posted May 15, 2016 Share Posted May 15, 2016 Finally, I could find out the problem. I checked all third party modules, one by one. and I found the corrupted one. it was a module for theme configuration. thanks for your helps Link to comment Share on other sites More sharing options...
PrestaHeroes USA Posted May 15, 2016 Share Posted May 15, 2016 Finally, I could find out the problem. I checked all third party modules, one by one. and I found the corrupted one. it was a module for theme configuration. thanks for your helps thanks for letting us know, please remember to visit community to help others. happy day, el Link to comment Share on other sites More sharing options...
Recommended Posts