Skip to content

šŸ•µļøā€ā™‚ļøCalculates and reports how Magento modules affect Magento2 DI compilation process and boostrapping process

Notifications You must be signed in to change notification settings

roma-glushko/mage-di-analyzer

Folders and files

NameName
Last commit message
Last commit date

Latest commit

Ā 

History

5 Commits
Ā 
Ā 
Ā 
Ā 
Ā 
Ā 
Ā 
Ā 
Ā 
Ā 
Ā 
Ā 

Repository files navigation

MageDIAnalyzer

MageDIAnalyzer helps to calculate and report how Magento modules affect Magento2 DI compilation process and boostrapping process.

Features:

  • šŸšØCalculates how many Kb each modules add to the DI metadata
  • šŸ“ˆCounts how many arguments, preferences, virtual types modules add to DI metadata files

Installation

The process is the same as for any other composer-based project:

git clone https://github.com/roma-glushko/mage-di-analyzer.git
cd mage-di-analyzer
composer install

Usage

Put your project to the production mode and copy DI metadata files from generated/metadata to the project tmp directory.

Then, MageDIAnalyzer will be able to check the files by running:

./bin/mage-di-analyzer analyze ./tmp/ -a global -f csv

Command Examples

./bin/mage-di-analyzer analyze ./tmp/ -a global -f csv
./bin/mage-di-analyzer analyze ./tmp/ -a adminhtml -f csv
./bin/mage-di-analyzer analyze ./tmp/ -a frontend -f csv
./bin/mage-di-analyzer analyze ./tmp/ -a crontab -f csv
./bin/mage-di-analyzer analyze ./tmp/ -a webapi_rest -f csv
./bin/mage-di-analyzer analyze ./tmp/ -a webapi_soap -f csv

Report Example

Module Name Area Arguments Argument Size Preferences Preference Size Instance Types Instance Type Size
Magento_Framework crontab 1995 714.79kB 335 38.44kB 57 6.25kB
Magento_Catalog crontab 1019 531.2kB 283 38.36kB 23 2.87kB

About

šŸ•µļøā€ā™‚ļøCalculates and reports how Magento modules affect Magento2 DI compilation process and boostrapping process

Topics

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages