1
0
mirror of synced 2024-12-16 08:06:02 +03:00
doctrine2/manual/en/improving-performance.txt

26 lines
1.2 KiB
Plaintext
Raw Normal View History

2010-04-06 22:36:40 +04:00
## Bytecode Cache
2010-04-06 22:36:40 +04:00
It is highly recommended to make use of a bytecode cache like APC. A bytecode cache removes the need for parsing PHP code on every request and can greatly improve performance.
> **NOTE**
2010-10-08 01:39:52 +04:00
> "If you care about performance and don't use a bytecode cache then you don't really care
2010-04-06 22:36:40 +04:00
> about performance. Please get one and start using it." (Stas Malyshev, Core Contributor
> to PHP and Zend Employee).
## Metadata and Query caches
2010-04-06 22:36:40 +04:00
2010-10-08 01:39:52 +04:00
As already mentioned earlier in the chapter about configuring Doctrine, it is strongly discouraged to use Doctrine without a Metadata and Query cache (preferably with APC or Memcache as the cache driver). 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.
2010-04-06 22:36:40 +04:00
## Alternative Query Result Formats
2010-04-06 22:36:40 +04:00
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.
## Apply Best Practices
2010-04-06 22:36:40 +04:00
A lot of the points mentioned in the Best Practices chapter will also positively affect the performance of Doctrine.