New Relic also has a blog post on how to debug Magento which I can recommend. Make sure there is some traffic on the shop tho. After installing it on your server and connecting the profile wait a couple of hours for data to come in. Unfortunately it's a paid service although they provide a free trial for pro accounts.
Last one is probably my favorite: New Relic. Check the Black fire site for more info how to use it. Just put your project on there and fire it up.
With a hackathon we set up a Vagrant box with black fire you can use. Since Aoe_Profiler is a module in Magento it doesn't show the underlying php processes and can crash on large installations with a lot of modules. Look out for any 3rd party modules that are taking up a lot of time or memory.Īnother great tool is Black fire. Those are the actual times it took a certain part of the code to process. On the front end it'll give you an output like this:Įxpand the results and check for large red blocks. For Magento I would recommend starting with Aoe_Profiler.
Profilers help you gain insight into whats going on in your code. The log will show you any query that takes longer than X seconds. Check out this post on how to turn it on. Magento can be quite heavy on the database so turning on the Slow Query Log might be a good place to start. Now if it's over, let's say, a second you might want to optimize.īefore you slap on some boosters and extra caching which isn't a fix just a patch or band aid to hide the real issue try to figure out what exactly is slow.
In the screenshot you can see it's quite low (200ms) so in this case the problem wouldn't be on the server but on front end. This is how long the script take to process on the server Check with the developer console in your browser for the Time To First Byte. First determine if it's front end rendering or the actual script execution that is slow.
0 kommentar(er)
