Needs review
Project:
Drupal core
Version:
main
Component:
routing system
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Issue tags:
Reporter:
Created:
3 Jun 2026 at 11:27 UTC
Updated:
26 Jun 2026 at 09:15 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #3
catchThis is green except performance tests. Want to actually do before/after profiling first before updating those.
Comment #4
catchAttaching before/after xhprof screenshots.
Looks like we save about 14ms in YAML parsing, and then 2ms is spent getting the new cache items from the persistent cache, so a net saving of 12ms (approximately).
But also shows that the total possible savings from YAML parsing (on admin/config/performance with Umami) is about 90ms, it'll be more on bigger sites with more modules. We won't be able to convert .info.yml or .services.yml but most other things should be fine.
We also have another 110ms from AttributeclassDiscovery which can get the same treatment.
So I think when both attribute and YAML discovery are converted, we'd be looking at about 200ms improvement on Umami cold cache web requests (minus whatever we can't save due to info/services parsing) (compared to an APCu cache miss) and more on larger sites.
Comment #5
catchComment #6
needs-review-queue-bot commentedThe Needs Review Queue Bot tested this issue. It no longer applies to Drupal core. Therefore, this issue status is now "Needs work".
This does not mean that the patch necessarily needs to be re-rolled or the MR rebased. Read the Issue Summary, the issue tags and the latest discussion here to determine what needs to be done.
Consult the Drupal Contributor Guide to find step-by-step guides for working with issues.
Comment #7
catchRebased.
Comment #8
needs-review-queue-bot commentedThe Needs Review Queue Bot tested this issue. It fails the Drupal core commit checks. Therefore, this issue status is now "Needs work".
This does not mean that the patch necessarily needs to be re-rolled or the MR rebased. Read the Issue Summary, the issue tags and the latest discussion here to determine what needs to be done.
Consult the Drupal Contributor Guide to find step-by-step guides for working with issues.
Comment #9
catch