⚡ Performance: Per-indexer loading and repeated config lookups in Indexer module

[lbajsarowicz]

Performance Issues in Magento_Indexer

Findings

#	File	Line(s)	Issue	Consensus Severity
39	Model/Indexer/Collection.php	64-74	N+1 Loading: For each indexer ID from config, loads individual indexer state via $indexer->load($indexerId), then iterates all states in nested loop to find match.	Medium

Methodology

• Static code analysis cross-validated by 3 AI systems (Claude, Codex gpt-5.4, Gemini 3 Pro)

[m2-assistant]

Hi @lbajsarowicz. 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.

[github-jira-sync-bot]

✅ Jira issue https://jira.corp.adobe.com/browse/AC-16864 is successfully created for this GitHub issue.

[sdouma]

The indexer collection is only loaded in the admin grid. The cron calls --group using the index registry.
You can refactor to eliminate the inner loop but if you want to eliminate the indexer->load then you have to refactor the indexer interface.
All of this for a small collection and marginal benefit on something that is rarely used.