25. Improving Performance¶
25.1. Bytecode Cache¶
It is highly recommended to make use of a bytecode cache like OPcache. A bytecode cache removes the need for parsing PHP code on every request and can greatly improve performance.
“If you care about performance and don’t use a bytecode cache then you don’t really care about performance. Please get one and start using it.”
「パフォーマンスに関心があり、バイトコードキャッシュを使用しない場合、パフォーマンスはあまり気にしません。入手して使い始めてください。」Stas Malyshev, Core Contributor to PHP and Zend Employee
Stas Malyshev、PHP および Zend Employee へのコア貢献者
25.2. Metadata and Query caches¶
As already mentioned earlier in the chapter about configuring Doctrine, it is strongly discouraged to use Doctrine without a Metadata and Query cache.
Operating Doctrine without these caches means Doctrine will need to load your mapping information on every single request and has to parse each DQL query on every single request. This is a waste of resources.
The preferred cache adapter for metadata and query caches is a PHP file cache like Symfony’s PHP files adapter. This kind of cache serializes cache items and writes them to a file. This allows for opcode caching to be used and provides high performance in most scenarios.
See Types of Caches
25.3. Alternative Query Result Formats¶
Make effective use of the available alternative query result formats like nested array graphs or pure scalar results, especially in scenarios where data is loaded for read-only purposes.
25.4. Read-Only Entities¶
You can mark entities as read only (See metadata mapping references for details).
This means that the entity marked as read only is never considered for updates. During flush on the EntityManager these entities are skipped even if properties changed.
Read-Only allows to persist new entities of a kind and remove existing ones, they are just not considered for updates.
See @Entity
You can also explicitly mark individual entities read only directly on the
UnitOfWork via a call to markReadOnly():
$user = $entityManager->find(User::class, $id);
$entityManager->getUnitOfWork()->markReadOnly($user);
Or you can set all objects that are the result of a query hydration to be marked as read only with the following query hint:
$query = $entityManager->createQuery('SELECT u FROM App\\Entity\\User u');
$query->setHint(Query::HINT_READ_ONLY, true);
$users = $query->getResult();
25.5. Extra-Lazy Collections¶
If entities hold references to large collections you will get performance and memory problems initializing them. To solve this issue you can use the EXTRA_LAZY fetch-mode feature for collections. See the tutorial for more information on how this fetch mode works.
25.6. Temporarily change fetch mode in DQL¶
See Temporarily change fetch mode in DQL
25.7. Apply Best Practices¶
A lot of the points mentioned in the Best Practices chapter will also positively affect the performance of Doctrine.
See Best Practices
