justbetter / magento2-xhprof-profiler
justbetter/magento2-xhprof-profiler
Xhprof profiler integration for Magento
Xhprof Profiler for Magento 2
Overview
This module integrates Xhprof profiling capabilities into your Magento 2 application. It provides an easy way to profile and analyze your application's performance by tracking and storing profiling data.
Requirements
- Magento 2.4.7 or higher
- Xhprof PHP extension
- Compatible with XHGui
- Compatible with Buggregator
Installation
-
Install via composer:
composer require justbetter/magento2-xhprof-profiler -
Enable the module:
bin/magento module:enable JustBetter_XhprofProfiler -
Run setup upgrade and di compile:
bin/magento setup:upgrade bin/magento setup:di:compile
Configuration for Buggregator
By default this module uses XHGui for processing the profiling data. We can use the Buggregator driver by overriding the default driver via xml:
<type name="JustBetter\XhprofProfiler\Model\Profiler\XhprofProfiler">
<arguments>
<argument name="driver" xsi:type="object">JustBetter\XhprofProfiler\Model\Profiler\Driver\Buggregator</argument>
</arguments>
</type>
Configure the module by adding the following configuration to your app/etc/env.php file:
return [
// ... other configurations ...
'xhprofprofiler' => [
'app_name' => 'Magento 247',
'endpoint' => 'http://exciting_chatelet.orb.local/profiler/store'
],
];
- app_name: The name of your application.
- endpoint: The endpoint where the profiling data will be stored.
Compatibility
This module is compatible with XHGui and Buggregator. These are graphical interfaces for viewing XHProf profiling data.
To integrate with XHGui:
- Follow the installation guide of XHGui at XHGui
- By default we use the default xhprof profiler and the results are getting uploaded to XHGui.
- Update default configuration via di.xml, check config.default.php for the possible options.
Default XHGui configuration
You can pass custom configuration to the XHGui driver via the arguments like the default configuration.
<type name="JustBetter\XhprofProfiler\Model\Profiler\Driver\XHGui">
<arguments>
<argument name="config" xsi:type="array">
<item name="profiler" xsi:type="string">xhprof</item>
<item name="save.handler" xsi:type="string">upload</item>
<item name="save.handler.upload" xsi:type="array">
<item name="url" xsi:type="string">http://xhgui.xhgui.orb.local/run/import</item>
<item name="timeout" xsi:type="number">3</item>
<item name="token" xsi:type="string">token</item>
</item>
</argument>
</arguments>
</type>
To integrate with Buggregator:
- Ensure Buggregator is installed and configured in your environment.
- Configure the endpoint in
app/etc/env.phpto point to Buggregator's profiling data endpoint.
Example configuration:
return [
// ... other configurations ...
'xhprofprofiler' => [
'app_name' => 'Magento 247',
'endpoint' => 'http://your_buggregator_instance/profiler/store'
],
];
Usage
The profiling is automatically enabled for all requests. The module uses the AppInterfacePlugin to start and terminate the profiler around each request.
Key Classes and Methods
-
XhprofProfiler- Methods:
__construct(): Initializes the profiler with the given driver and optional tags.handle(): Starts the profiler.terminate(): Ends the profiler and stores the profiling data.
- Methods:
-
AppInterfacePlugin- Methods:
aroundLaunch(): Wraps around the application launch to start and stop the profiler.
- Methods:
License
This project is licensed under the MIT License - see the LICENSE file for details.
Contributing
- Fork the repository.
- Create your feature branch (
git checkout -b feature/fooBar). - Commit your changes (
git commit -am 'Add some fooBar'). - Push to the branch (
git push origin feature/fooBar). - Create a new Pull Request.
Contact
If you have any questions or need further assistance, please contact [[email protected]].
By following this README, you should be able to integrate and use the Xhprof Profiler in your Magento 2 application effectively. Happy profiling!
No changelog yet
The vendor hasn't published a changelog. Tagged releases appear in the Versions tab.
Requires 5
| Package | Constraint |
|---|---|
| magento/framework | * |
| magento/module-config | ^101.2 |
| perftools/php-profiler | ^1.1 |
| php | >=8.2 |
| spiral-packages/profiler | ^1.2 |
Requires-dev 2
| Package | Constraint |
|---|---|
| bitexpert/phpstan-magento | ^0.30.1 |
| phpstan/phpstan | ^1.10 |
Compatibility
Each Magento release line is installed on its supported PHP versions, then the module is built (DI compilation + static-content deploy) and its unit and integration suites are run. The matrix shows the lines and PHP versions the module is confirmed to install and run on. Code-quality results further down (phpstan, phpcs, …) are reported separately and never affect compatibility.
Code Quality
Advisory checks against the module's source. Static analysis runs once across the whole module; PHPStan re-runs per Magento + PHP version because resolvable symbols differ between releases. These NEVER affect the Compatibility badge. A phpcs finding can't make a module incompatible.
Static analysis
Coding standards (phpcs), mess detection (phpmd), copy-pasted code (cpd), PHP cross-version compatibility, composer.json validity. Each runs once for the whole module.
| Tool | Status | Findings | Summary |
|---|---|---|---|
| PHPCS | Fail | 10 | 2 errors, 8 warnings (ruleset: Magento2) — 7 auto-fixable with phpcbf |
| PHPMD | Warning | 2 | 2 rule violations (MissingImport:1, UnusedFormalParameter:1) |
| Cpd | Pass | 0 | |
| Composer validate | Info | 1 | valid; 1 advisory note (composer validate --strict) |
Tests
Unit and integration suites, run for each applicable Magento and PHP version. A test failure speaks to the module's behaviour, not its compatibility with a Magento line, so it is reported here separately and never reddens the compatibility matrix.
Unit tests
| Magento | PHP 8.2 | PHP 8.3 | PHP 8.4 | PHP 8.5 |
|---|---|---|---|---|
| 2.4.7 | N/A | N/A | ||
| 2.4.8 | N/A | N/A | ||
| 2.4.9 | N/A | N/A |
Integration tests
| Magento | PHP 8.2 | PHP 8.3 | PHP 8.4 | PHP 8.5 |
|---|---|---|---|---|
| 2.4.7 | N/A | N/A | ||
| 2.4.8 | N/A | N/A | ||
| 2.4.9 | N/A | N/A |
Security
Security checks run directly against the module: an audit of its declared dependencies for known vulnerabilities (composer audit) and a scan of its source for malware and web-shell signatures. Each runs once. A malware detection fails the version outright.
More from justbetter
View vendorMagento 2 Environment Config Import
Magento 2 Filter for Sentry Events
Customer specific pricing module for Magento 2
Magento2 bundle for extending the Akeneo connector with awesome features.
Turn an existing module into recurring revenue.
If you already maintain a Magento 2 module on GitHub or GitLab, listing it on Packagento takes about five minutes. We mirror your tags, handle distribution signing, and route paid licenses through Stripe Connect, so you can keep shipping the way you already do.