The ProfilerLog extension logs all profiler-data to its own database-table - as simple as that. But by doing this, it allows you to to profile Magento over a period of time, which is vital for analysing Magento performance under different server loads. Not only that, ProfilerLog also gives you numerous nice graphics from within the Magento backend. A developers must.
Want to see ProfilerLog for Magento in action?
I bought this module as I was having trouble with my Magento Admin Panel running slowly and needed to find out what pages and when the system was running slowly. This module tracks all pages over time and gives you a great picture of whats going on behind the scenes. Would recommend for any Magento administrator
When you are experiencing performance-issues with Magento, profiling is key. With profiling you can see which resources are eating up the page. But the standard Magento profiler (and various other third party profilers) only allow you to profile a single page, because the profiling data are added to the bottom of the page. Performance-bottlenecks that seem to occur randomly can not be traced, because nothing of the profiler-data is logged.
This is what our ProfilerLog extension changes: It logs various performance-related details to the Magento database, for later inspection. You can either use the ProfilerLog pages in your Magento Admin to analyse things using statistics-based charts, or you can dive into the details by inspecting the database-table profilerlog_log.
By using these data, you can easily inspect specific bottlenecks:
Charts are drawn in the Magento backend by using a set-interval (for instance, 3 minutes) and a period (the last 24-hours). The following graphical charts are available in the Magento backend:
We will be working on adding more details to the log, as long as this doesn't flood the system too much.
All profiler-data is logged to the Magento database into a single flat MyISAM table. Inserting new entries to this table costs little extra overhead, so is quite harmless. Ofcourse it costs you an extra database-query for every request, so it is not recommended to have ProfilerLog running continuously.
Another reason to turn on ProfilerLog only when you're actually profiling, is the amount of disk-space consumed by the profilerlog_log table. On average, one record takes up about 1 Kb, which is not much. But having a busy site with 25.000 hits per day will leave you with a 1Gb table after 40 days. We recommend you keep things running for a few days, analyse things and clean up the table afterwards.