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
Symfony 3.2 introduces a new config cache metadata ClassExistenceResource.
It assumes the cache is not fresh when the class is added or lost since previous check.
If I enable the doctrine_integration config of this bundle, the proxy of EntityManager will be generated.
And the proxy would be assumed not to exist at the first time of Kernel initializes container because it's never loaded as far as I don't retrieve the EntityManager from the container.
But If the container is initialized after the EntityManager was retrieved previous time, the existence state of it was changed, so cache miss happens.
This thing has no problem on almost every HTTP requests, destroying the class existence info after request and second check never happens.
However on the functional tests, the container will be initialized many times, it means container cache miss always occurs from second test case which relies on Kernel and container.
It leads testsuite to be significant bad performance.
The text was updated successfully, but these errors were encountered:
Symfony 3.2 introduces a new config cache metadata ClassExistenceResource.
It assumes the cache is not fresh when the class is added or lost since previous check.
If I enable the
doctrine_integration
config of this bundle, the proxy of EntityManager will be generated.And the proxy would be assumed not to exist at the first time of Kernel initializes container because it's never loaded as far as I don't retrieve the EntityManager from the container.
But If the container is initialized after the EntityManager was retrieved previous time, the existence state of it was changed, so cache miss happens.
This thing has no problem on almost every HTTP requests, destroying the class existence info after request and second check never happens.
However on the functional tests, the container will be initialized many times, it means container cache miss always occurs from second test case which relies on Kernel and container.
It leads testsuite to be significant bad performance.
The text was updated successfully, but these errors were encountered: