Download the PHP package monogo/optimize-object-manager without Composer
On this page you can find all versions of the php package monogo/optimize-object-manager. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download monogo/optimize-object-manager
More information about monogo/optimize-object-manager
Files in monogo/optimize-object-manager
Package optimize-object-manager
Short Description Magento 2 module to optimize Compiled ObjectManager
License MIT
FAQ
Example:
In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
- Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
- To use Composer is sometimes complicated. Especially for beginners.
- Composer needs much resources. Sometimes they are not available on a simple webspace.
- If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
- Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Informations about the package optimize-object-manager
Magento 2 module to optimize Compiled ObjectManager.
This module will work only with Magento 2.3.4 and higher
Important
This is experimental functionality, You are using it at your own risk !
Install
Composer
In perfect world, command
should do the job.
But in few cases, composer do not recognize patch files.
If you don't see line
run
Add in your composer.json
Run
You should see line
if not, go to vendor/magneto and remove framework directory, then re-run
Magento Setup
-
Run Magento commands
- Make sure your that Magento 2 instance is running in Production mode and after installation generated/metadata directory is not empty
Configuration Options
Edit app/etc/env.php
add lines:
- enabled - 0 or 1
- allowed_area - Magento 2 area (frontend,adminhtml,crontab,webapi_rest,webapi_soap,...) .
Check
After installation and configuration, you should see new files in generated/metadata , for example:
- __frontend_global_diff.php
- __adminhtml_global_diff.php
How it works
When you are using M2 in Production mode and generated/metadata directory is not empty, magento is using Compiled mode in Object Manager.
Generated files contains all classes and are heavy.
In my case it was >8 MB per one area file.
Magento is loading global.php file and after that your area file (for example frontend.php).
This module is calculating diff between global.php and given area, and it is saving new file __[area_code]_global_diff.php
If diff file exists, it is coping loaded global config to given area, and it is patching config with the diff.
The original area file (for example frontend.php) is skipped.
In my case (API call) it improved simple request by 14% of time and 33% of memory used.
