A whole lot of new features in this release:

• any existing timing point from Debug Output can be traced
• it is possible to trace those pages which terminate with a redirect / direct exit (eg ezjscore calls, login pages) by registering a php method as ezexecution cleanup handler
• some some php classes have been included, which can be used to measure db timings and cluster-db timings also when the standard Debug Output is disabled

And the BIG ONE: Munin integration!

- any variable traced by ezperformancelogger can be visualized in (or hidden from) munin graphs

- both peak and average-per-page values can be graphed

- custom label and other graph attributes can be set via eZ ini files

Here is a sample Munin page graphing execution-time, db-queries and memory-usage per eZ page: http://gggeek.altervista.org/sw/Munin_localhost.localdomain.htm#ez%20performance%20logger