Why does Magento’s bootstrap feel slow?

[MagePsycho]

⚙️⏱️ Why does Magento’s bootstrap feel slow? 🤔
Is it autoloading?
On every request, PHP resolves hundreds or thousands of classes across many modules—that’s a lot of filesystem I/O and autoloader lookups.

How to speed it up ⚡️
Composer/autoload: composer install --no-dev --optimize-autoloader or composer dump-autoload -o or via some other mechanism?

Let’s discuss.

[m2-assistant]

Hi @MagePsycho. Thank you for your report.
To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce.

• For more details, review the Magento Contributor Assistant documentation.
• Add a comment to assign the issue: @magento I am working on this
• To learn more about issue processing workflow, refer to the Code Contributions.

---

Join Magento Community Engineering Slack and ask your questions in #github channel.
⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
🕙 You can find the schedule on the Magento Community Calendar page.
📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

[senthilengg]

@MagePsycho Raj, is it not the same DI compile is doing in production mode.

[MagePsycho]

@MagePsycho Raj, is it not the same DI compile is doing in production mode.

AFAIK setup:di:compile will not optimize the composer autoloading.
Maybe opcaching/preloading to rescue here?

[hostep]

@MagePsycho: I would advise you to run composer dump-autoload -o after executing setup:di:compile, so the files from the generated/code directory are included in the optimised autoloader.

[m2-assistant]

Hi @engcom-Hotel. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• 4. Verify that the issue is reproducible on 2.4-develop branch
  Details

  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!
• 5. Add label Issue: Confirmed once verification is complete.
• 6. Make sure that automatic system confirms that report has been added to the backlog.

[engcom-Hotel]

Hello @MagePsycho,

I hope you have gone through with the @hostep comment here, please let us know if you have any further query on this.

Thanks