A couple of weeks ago I created a sub-domain for extensions and styles demo.
You will find it here: BBCodes Demo
Its a basic phpBB installation with only my released extension and styles.
So what you see there is how it looks on a default prosilver installation.
At the bottom of the Forum and Portal pages you will find the Performance Tester.
Its a tool that measure performance and load of my extensions.
Steve got the original idea and I did a little something to get what I wanted from it.
Demo Site
Demo Site
The first version of the extension is ready.
The main functions of the performance_tester extension
1. Public performance statistics block
Displays a special block with performance metrics in the forum footer or in other places (as configured).
The block displays:
SQL — SQL query execution time (if possible).
PHP — PHP code execution time.
Total — total page generation time.
Queries — number of SQL queries.
Memory — amount of memory used.
2. Extension profiling
After patching the core, the extension can show:
How much time, memory, and SQL queries each event listener of the extension spent.
Sums up this data for each extension (vendor/extension).
This allows you to identify which extensions have the greatest impact on forum performance.
3. Flexible settings
In the admin panel, you can:
Turn on/off the display of the block.
Limit block visibility to specific user groups or administrators only.
Configure which metrics to show (time, memory, requests).
Configure block position in template (before/after footer, etc.).
4. Minimal intervention in core
Does not require core edits for basic operation.
A core patch (EventDispatcher) is required for extension profiling.
5. Debugging information
Can output debug data (e.g. arrays with profiling results) — at the developer's discretion.
How it works
Data collection
Time, memory, and number of SQL queries are recorded at the beginning and end of page generation.
After the core patch — the same parameters are recorded for each extension event listener.
Transfer to template
All data is transferred to the template via assign_vars and assign_block_vars.
The template has a nice-looking output of cards with metrics.
Display
The block is visible only to those user groups that are allowed by the settings.
You can quickly evaluate the forum performance and the impact of extensions.
Why is this necessary
For the administrator — to see how fast the forum works, how many resources are spent on generating pages.
For the developer — to identify “heavy” extensions and optimize them.
For the tester — to compare performance before and after installing new extensions.
Demo: picnic-tv.com
The main functions of the performance_tester extension
1. Public performance statistics block
Displays a special block with performance metrics in the forum footer or in other places (as configured).
The block displays:
SQL — SQL query execution time (if possible).
PHP — PHP code execution time.
Total — total page generation time.
Queries — number of SQL queries.
Memory — amount of memory used.
2. Extension profiling
After patching the core, the extension can show:
How much time, memory, and SQL queries each event listener of the extension spent.
Sums up this data for each extension (vendor/extension).
This allows you to identify which extensions have the greatest impact on forum performance.
3. Flexible settings
In the admin panel, you can:
Turn on/off the display of the block.
Limit block visibility to specific user groups or administrators only.
Configure which metrics to show (time, memory, requests).
Configure block position in template (before/after footer, etc.).
4. Minimal intervention in core
Does not require core edits for basic operation.
A core patch (EventDispatcher) is required for extension profiling.
5. Debugging information
Can output debug data (e.g. arrays with profiling results) — at the developer's discretion.
How it works
Data collection
Time, memory, and number of SQL queries are recorded at the beginning and end of page generation.
After the core patch — the same parameters are recorded for each extension event listener.
Transfer to template
All data is transferred to the template via assign_vars and assign_block_vars.
The template has a nice-looking output of cards with metrics.
Display
The block is visible only to those user groups that are allowed by the settings.
You can quickly evaluate the forum performance and the impact of extensions.
Why is this necessary
For the administrator — to see how fast the forum works, how many resources are spent on generating pages.
For the developer — to identify “heavy” extensions and optimize them.
For the tester — to compare performance before and after installing new extensions.
Demo: picnic-tv.com