aoepeople/aoe_profiler

Magento Profiler

Maintainers

Details

github.com/AOEpeople/Aoe_Profiler

Homepage

Source

Issues

Installs: 19 556

Dependents: 0

Suggesters: 0

Security: 0

Stars: 244

Watchers: 71

Forks: 101

Open Issues: 29

Type:magento-module

v0.3.0 2013-10-27 00:28 UTC

Requires

OSL-3.0 384b6de6443b383fcc62ed4c4f76604e2c256c51

  • Fabrizio Branca

This package is not auto-updated.

Last update: 2024-12-21 19:32:59 UTC

README

Build Status

http://www.fabrizio-branca.de/magento-profiler.html

For the Magento 2 version of this extension, please visit: https://github.com/perryholden/Holdenovi_Profiler

Usage

Copy the aoe_profiler.xml.sample file to var/aoe_profiler.xml and find some documentation on what the settings mean in that file.

Find some more settings in System > Configuration > Developer > Debug > Profiler.

Enable database profiling

Add this to your local.xml:

<config>
    <global>
        <resources>
            <default_setup>
                <connection>
                    <profiler>1</profiler>
                </connection>
            </default_setup>
        </resources>
    </global>
</config>

Notes

Depending on the complexity of your site a lot of data ends up being collected during a profile run. The first problem with this is that the database table holding this information might be growing. Please double check the cron settings of the cleanup task.

By default MySQL comes with max_allowed_packet set to 1 MB. One profile run could exceed 1 MB. Please check var/system.log for error messages and increase this setting in our MySQL server settings (/etc/mysql/myconf). (Also see: http://dev.mysql.com/doc/refman/5.1/en/packet-too-large.html)

[mysqld]
max_allowed_packet=16M