⚡ Performance: Per-lookup ObjectManager calls and URL path variation overhead in UrlRewrite module

[lbajsarowicz]

Performance Issues in Magento_UrlRewrite

Findings

#	File	Line(s)	Issue	Consensus Severity
109	Model/Storage/DbStorage.php	115-122, 140-171	Expensive Loop Ops: Creates 4 URL path variations (trimmed/untrimmed, encoded/decoded) per lookup, executes fetchAll on all variants, then O(n) scan with string operations per result.	Medium-High
107	Model/CompositeUrlFinder.php	75-76, 91-92	Expensive Loop Ops: ObjectManager->get() per child finder on every URL lookup. getChildren() also runs uasort() on every call.	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-16856 is successfully created for this GitHub issue.