You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The upcoming Symfony 5.0 release gives us once-in-a-two-years opportunity to improve things. I'd like to improve this: events/listeners take too much time in the "dev" environment.
Symfony\Component\HttpKernel\Debug\TraceableEventDispatcher::getNotCalledListeners is the slowest part of the application and takes 15% of the total time.
Symfony\Component\EventDispatcher\Debug\WrappedListener::getWrappedListener is called 5,135 times
Symfony\Component\EventDispatcher\Debug\TraceableEventDispatcher::getListenerPriority is called 279 times
Can someone please take a look why this is so slow ... and see if we can improve it even if it requires making some minor breaking changes? Thanks!
The text was updated successfully, but these errors were encountered:
…y once (xabbuh)
This PR was merged into the 4.3 branch.
Discussion
----------
[EventDispatcher] collect called listeners information only once
| Q | A
| ------------- | ---
| Branch? | 4.4
| Bug fix? | no
| New feature? | yes
| BC breaks? | no
| Deprecations? | no
| Tests pass? | yes
| Fixed tickets | #31970
| License | MIT
| Doc PR |
Commits
-------
284262a collect called listeners information only once
Description
The upcoming Symfony 5.0 release gives us once-in-a-two-years opportunity to improve things. I'd like to improve this: events/listeners take too much time in the "dev" environment.
Look at this profiling of the Symfony Demo app: https://blackfire.io/profiles/f35213c7-d5b5-4eb4-8315-4ad3f24ac9e9/graph
Some things that look "wrong":
Can someone please take a look why this is so slow ... and see if we can improve it even if it requires making some minor breaking changes? Thanks!
The text was updated successfully, but these errors were encountered: