The 2026 Drupal Business Survey is open. Your response will help shape the future of the Drupal business ecosystem.Whilst profiling I found some services that could be marked lazy - we might choose do try to ensure these services are not needed instead of marking them lazy but at least it gives us a clue about where some potential optimisations are.
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | 2508519.1.patch | 23.59 KB | alexpott |
Comments
Comment #1
alexpottFrontpage view, anonymous, no render cache with 1 node.
Comment #3
dawehnerMh, so this probably doesn't give us that much of an advantage as the container gets much bigger with that approach.
I think doing this again with #2408371: Proxies of module interfaces don't work applied would be actually really interesting to see, as this gives us an idea how costly it has been to dump all those classes into the container.
Comment #17
smustgrave commentedThank you for creating this issue to improve Drupal.
We are working to decide if this task is still relevant to a currently supported version of Drupal. There hasn't been any discussion here for over 8 years which suggests that this has either been implemented or is no longer relevant. Your thoughts on this will allow a decision to be made.
Since we need more information to move forward with this issue, the status is now Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.
Thanks!
Comment #18
catchI think the difficulties with lazy services is probably covered by #3514491: [meta] Replace lazy service proxy generation with service closures and we can look at individual examples there.
Comment #19
smustgrave commentedRock on!