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.