1

I have some modules that I'm not going to use. E.g Temando_Shipping, MSI modules, GraghQl modules,...

Should I disable them using config.php or should I remove them from the codebase using composer replace?

Which one is the better approach and has a better performance result?

  • Better performance is to remove github.com/yireo/magento2-replace-all but you will have issues to work though every time you add or remove extension or upgrade core. – Dominic Xigen May 30 at 23:10
  • Give it a try on a test vanilla store with sample data github.com/DominicWatts/Benchmark – Dominic Xigen May 30 at 23:16
  • Biggest issue for me was MSI. Early versions of MSI really slowed down some stores in dev magento.stackexchange.com/questions/292214/… fortunately recent upgrades / patches have fixed some of the issues – Dominic Xigen May 30 at 23:27
  • @DominicXigen Thanks, I've used this package github.com/yireo/magento2-replace-inventory before. I'm just wondering how fast it is comparing to disabling the modules, thoughts? – Toan Tam Jun 1 at 7:40
  • Using that benchmark script I got about 30% improvement on a demo store on saving products. But I implemented on an actual project and as soon as I started adding third party extensions I had problems. But I saw about a 20% improvement on applying MSI upgrade which included their patches. The amazon payment modules stood out for adding noticable load but I could never figure out why. – Dominic Xigen Jun 1 at 18:25
0

Disabling the Unused modules is the best approach and it has good performance result. Removing them completely from code base may have unintended side effects.

| improve this answer | |
  • Thanks. How do you compare the performance between disabling the modules vs removing them? – Toan Tam Jun 1 at 7:42

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.