Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Performance issues in Symfony 6.4 #383

Open
kopfsalat opened this issue Dec 19, 2023 · 0 comments
Open

Performance issues in Symfony 6.4 #383

kopfsalat opened this issue Dec 19, 2023 · 0 comments
Labels
bug Something isn't working

Comments

@kopfsalat
Copy link

Q A
auditor-bundle version 5.4
PHP version 8.2
Database MySQL 8

Summary

Hi,

after upgrading from Symfony 5.4 to 6.4, we noticed a performance impact on our integration tests when the auditor-bundle is enabled. This issue only affects tests that flush data. We were able to identify the root cause as the handling of events (dispatchEvent()) in Symfony\Bridge\Doctrine\ContainerAwareEventManager.

Disabling the auditor-bundle via config (just enabled: false) restored the tests to their usual performance.

The performance difference is significant, with each test taking approximately 9 seconds when auditor-bundle is enabled and less than 1 second when disabled.

However, this difference only seems to be present in our development environment. We have not observed these issues in our staging environment or in our test step in the ci/cd pipeline. I disabled xdebug to see if this could be related, but unfortunately it isn't. I'm running out of time to debug this further and it's perfectly fine to have the auditor bundle disabled in dev for now.

Let me know if this report is of interest and if you have specific questions. I can then spend some more time on it.

Current behavior

In our dev environment with Symfony 6.4, integration test performance has significantly decreased by a factor of 9 compared to when we were using Symfony 5.4.

How to reproduce

Currently, I am unable to provide all the details regarding our development infrastructure, and I am uncertain about the root cause of this issue. However, as previously stated, I can conduct further investigation if necessary.

Expected behavior

Almost no performance change, I guess :-)

@kopfsalat kopfsalat added the bug Something isn't working label Dec 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant