![]() ![]() The only thing xdebug needs to do is collect info for it's stack trace. What i do find surprising is that with the above settings no actual debugging/profiling is enabled. This might be a tip for people experiencing bad performance in relation to xdebug. Xdebug.profiler_output_dir = "c:/wamp/tmp"Īfter commenting out all of the above, basically disabling xdebug altogether, my PW installs where back to normal, snappy performance.īecause i don't use xdebug for debugging or profiling i'm fine with totally disabling it. A solution could be to change the port on which is being listened (as Mithun Sen has said). Xdebug.profiler_output_name = cachegrind.out.%t.%p It is also possible that some other service is running on port 80 (maybe IIS Express, some Torrent clients, Skype.). In Wampserver it comes bundled with the following settings in php.ini (to which i added the max_nesting_level because the default 100 will cause problems in PW) : This was not at all the case with the live site running the same code base.Īfter some hair-pulling i discovered that it was xdebug slowing things down. Especially opening a template edit page performed bad, with a noticeable 2 to 3 seconds delay in the response. ![]() After logging in i also noticed this in the back-end. Having set up an existing project and a vanilla PW install i noticed that some front-end pages took quite long to respond/render. Having used it in the past with no problems i decided to use Wampserver 2.5 to setup my webdev environment. This afternoon i was setting up a new laptop with Win7 64bits. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |