Skip to content

Should the Doctrine Cached reader be used? #83

@drdamour

Description

@drdamour

I was reading through the doctrine annotations docs trying to resolve a problem and i came across http://docs.doctrine-project.org/projects/doctrine-common/en/latest/reference/annotations.html#setup-and-configuration which says:

"This creates a simple annotation reader with no caching other than in memory (in php arrays). Since parsing docblocks can be expensive you should cache this process by using a caching reader."

Does turning on injection cacheing negate the performance benefits of annotation cacheing? Or should the injection layer be using a cached annotation reader as well?

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions