Magento Open Source vs. Adobe Commerce performance
After reading this misleading Adobe (https://info2.magento.com/rs/585-GGD-959/images/eBook_Open%20Source%20Myths_021919.pdf?utm_source=marketo&utm_medium=email&utm_campaign=1904-DG-WP-Open-Source-Myths) marketing story about how good Magento Enterprise is vs. Open Source, I have decided to check performance.
Let's break this Adobe Enterprise Myth!
Myth: Magento Open Source and Magento Commerce offer the same performance benefits
TRUTH With Magento Commerce, you have significantly less risk of site crashes and slow speeds due to traffic surges.
In the reality Adobe Commerce has more bugs and performance issues. Especially wen merchants what’s to use Adobe Commerce as a basement framework to build something grate. And never consider Adobe Commerce Cloud if you need performance. Adobe cloud works good only for low traffic websites. Helly Hansen moved out from the Adobe Cloud and received a great performance improvement. Just by moving to a AWS cloud they improved performance two times without any code changes. Adobe Commerce Cloud Hosting white label offering of the Platform.sh designed for Drupal and Word Press and is just a garbage up$ell offering to your Magento license.
Our Adobe Commerce test Environment:
- AWS EC2 C5.large 2vCPU 4GB
- RDS 2vCPU 4GB
- ElasticCache Redis 2GB T2.medium
- The same environment for both tests.
- Magento 2.3.3 CE and EE Core + sample data without any customizations
You can check sites here:
Magento 2.3.3 CE
Magento 2.3.3 EE
Test url. Doesn’t work any more. And I removed the links.
For the test, I used ab (Apache Benchmark) tools with concurrency 1 tests numbers 10 result median waiting time.
ab -n 10 -c 1 http://m2ce.umsf-it.dp.ua/gear/bags.html
The test was made from another EC2 T2. A micro instance in the same AWS region us-west-1 California/San Jose to avoid network latency
Test cases:
1.Home Page
M2CE
Result: 69ms
M2EE:
Result: 94ms
2. Category Page
M2CE:
Result: 198ms
M2EE:
Result: 214ms
3. Simple Product Page
M2CE:
Result: 172ms
M2EE:
Result: 206 ms
4. Configurable product
M2CE:
Result: 182 ms
M2EE:
Result: 219 ms
5. Cart page (Empty)
M2CE:
Result: 81
M2EE:
Result: 99
8. Search
M2CE:
Result: 199 ms
M2EE:
Result: 223 ms
You can check why it’s happened comparing Profiler Data of the main page:
Magento 2 CE:
Timeline:
Functions Calls:
Magento EE:
Timeline:
Functions Calls:
Basically, EE has more MySQL queries 32 vs. 18. Also, we have a fuckup with MySQL connection on CE version 22ms vs. 1ms. Magento CE should be 20 ms faster, as we can see from the median of 10 results of the first test case.
Also, M 2 EE always generates Ajax Requests for a banner. Then general scalability is worse than in this case. EE has some scalability improvement (split database solutions ), but it is so useless even Magento Cloud doesn’t use it. Better to go with Magento NodeJS micro-services than with Adobe Commerce
Pivot Data Magento 2.3 CE vs. Magento 2.3 EE
+-------------------------+-------------------------------------+
| | Page Response Time (less is better) |
+-------------------------+--------------+-------------+--------+
| | Magento 2CE | Magento 2EE | Diff |
+-------------------------+--------------+-------------+--------+
| 1. Main Page | 69 | 94 | 36.23% |
+-------------------------+--------------+-------------+--------+
| 2. Category | 198 | 214 | 8.08% |
+-------------------------+--------------+-------------+--------+
| 5. Product Simple | 172 | 206 | 19.77% |
+-------------------------+--------------+-------------+--------+
| 6. Product Configurable | 182 | 219 | 20.33% |
+-------------------------+--------------+-------------+--------+
| 7. Cart Page | 81 | 99 | 22.22% |
+-------------------------+--------------+-------------+--------+Adobe Enterprise myth killed!! It is much slower and over-advertised solution. That’s why the big corporations killed Magento Opens Source. To sell garbage they should remove other option.
