PHPackages                             maritos/magento2-performance-fixes - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. maritos/magento2-performance-fixes

ActiveLibrary

maritos/magento2-performance-fixes
==================================

Magento 2 performance fixes.

1.0.1(4y ago)6321.1k—0%7[3 issues](https://github.com/maritos/magento2-performance-fixes/issues)MITPHP

Since Jul 9Pushed 4y ago7 watchersCompare

[ Source](https://github.com/maritos/magento2-performance-fixes)[ Packagist](https://packagist.org/packages/maritos/magento2-performance-fixes)[ RSS](/packages/maritos-magento2-performance-fixes/feed)WikiDiscussions main Synced today

READMEChangelog (2)Dependencies (1)Versions (3)Used By (0)

magento2-performance-fixes
==========================

[](#magento2-performance-fixes)

Performance fixes for magento 2 core.

Problem and solution's concept - briefly
========================================

[](#problem-and-solutions-concept---briefly)

PHP / Magento doesn't support concurency requests. When Magento is handling numbers of requests at the same time (e.g. some headless frontend sent 10 requests at the same time on page load to ask graphql api for data) then each request got information to start building a cache. If cache exists - everything works perfectly but if it doesn't then first request starts building the cache and each next request do the same too.

It's not hard to imagine situation that when some process is slow and takes for instance 2s then every request will try build a cache until building process has been completed by one of requests. It is leading to situation when N requests are doing the same thing and every new request make process slower and slower the process which started before. Finally when we are talking about high traffic websites it's cause redis crash / high and long disk/cpu usage etc.

IMPORTANT: **Testing just one request (without high concurrency) you likly won't achive any speed improvments.**

[![Conecept](https://camo.githubusercontent.com/9f9d0a5066074a9a567da73ecba96c8b090eecafe532985e5523a6f8c72fe0de/68747470733a2f2f692e6962622e636f2f6470325032506e2f636f6e636570742d70726f626c656d2d736f6c76652e706e67)](https://camo.githubusercontent.com/9f9d0a5066074a9a567da73ecba96c8b090eecafe532985e5523a6f8c72fe0de/68747470733a2f2f692e6962622e636f2f6470325032506e2f636f6e636570742d70726f626c656d2d736f6c76652e706e67)

Requirements
============

[](#requirements)

One dependancy: `cweagans/composer-patches`

Compatibility
=============

[](#compatibility)

This solution provides 3 file changes in core:

- \#1 - magento/framework/Config/Data.patch - *2.3.0+*
- \#2 - magento/framework/App/ObjectManager/ConfigLoader.patch - *2.2.0+*
- \#3 - magento/framework/Interception/Config/Config.patch - *2.2.0+*

Instalation
===========

[](#instalation)

For this fixes I have chosen fix by vendor's patch. According Magento 2 documentation here:

1. Step one

install package by composer:

`composer require maritos/magento2-performance-fixes`

2. Extend composer.json

```
    "extra": {
        "enable-patching": true,
        "magento-force": "override",
        "composer-exit-on-patch-failure": true,
        "patches": {
            "magento/framework": {
                "performance fix #1 - vendor/magento/framework/Config/Data.php": "vendor/maritos/magento2-performance-fixes/vendorPatch/magento/framework/Config/Data.patch",
                "performance fix #2 - vendor/magento/framework/App/ObjectManager/ConfigLoader.patch": "vendor/maritos/magento2-performance-fixes/vendorPatch/magento/framework/App/ObjectManager/ConfigLoader.patch",
                "performance fix #3 - vendor/magento/framework/Interception/Config/Config.patch": "vendor/maritos/magento2-performance-fixes/vendorPatch/magento/framework/Interception/Config/Config.patch"
            }
        }
    }

```

3. composer install

After `composer install` make sure patches has been applied. Composer install output should similar to:

```
  - Applying patches for magento/framework
    vendor/maritos/magento2-performance-fixes/vendorPatch/magento/framework/Config/Data.patch (performance fix #1 - vendor/magento/framework/Config/Data.php)
    vendor/maritos/magento2-performance-fixes/vendorPatch/magento/framework/App/ObjectManager/ConfigLoader.patch (performance fix #2 - vendor/magento/framework/App/ObjectManager/ConfigLoader.patch)
    vendorPatch/magento/framework/Interception/Config/Config-2.4.x.patch (performance fix #3 - vendor/magento/framework/Interception/Config/Config.patch)

```

Contributing
============

[](#contributing)

Happy to hear your suggestions :)

Testing this solution
=====================

[](#testing-this-solution)

Please give me feedback via linkedin  what improvment you achived. I will really appriciate it!

Thanks!

###  Health Score

34

—

LowBetter than 79% of packages

Maintenance19

Infrequent updates — may be unmaintained

Popularity40

Moderate usage in the ecosystem

Community13

Small or concentrated contributor base

Maturity52

Maturing project, gaining track record

 Bus Factor1

Top contributor holds 100% of commits — single point of failure

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

###  Release Activity

Cadence

Every ~187 days

Total

2

Last Release

1530d ago

### Community

Maintainers

![](https://www.gravatar.com/avatar/228a5a9988f7cccf787c61bbd144068b5247eb2d0f4d3b5f82dacceba23eae47?d=identicon)[maritos](/maintainers/maritos)

---

Top Contributors

[![maritos](https://avatars.githubusercontent.com/u/8460801?v=4)](https://github.com/maritos "maritos (6 commits)")

### Embed Badge

![Health badge](/badges/maritos-magento2-performance-fixes/health.svg)

```
[![Health](https://phpackages.com/badges/maritos-magento2-performance-fixes/health.svg)](https://phpackages.com/packages/maritos-magento2-performance-fixes)
```

###  Alternatives

[symplify/vendor-patches

Generate vendor patches for packages with single command

1866.4M25](/packages/symplify-vendor-patches)[openmage/magento-lts

A fork of Magento-1 that is accepting bug fixes (backward compatible, drop in replacement for official Magento)

917227.3k19](/packages/openmage-magento-lts)[civicrm/civicrm-core

Open source constituent relationship management for non-profits, NGOs and advocacy organizations.

718267.0k10](/packages/civicrm-civicrm-core)[goalgorilla/open_social

Open Social is a distribution for building social communities and intranets.

193457.5k](/packages/goalgorilla-open-social)[thunder/thunder-distribution

The thunder distribution

51625.6k3](/packages/thunder-thunder-distribution)[acquia/orca

A tool for testing a company's software packages together in the context of a realistic, functioning, best practices Drupal build

32896.7k](/packages/acquia-orca)

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)
