We were already using APC for the whole application. Turning on APC specifically for metadata doesn't seem to help on the problem we're trying to solve. It would be nice if we were caching annotations metadata, the same way we're doing with proxies, for instance.
One more thing about the Parser, when Stof (Doctrine Extensions, say Sluggable) or Form require files with annotations to be parsed, it takes the @var , @author , etc... as valid tags and tries to find a file like: ...../symfony/src/Symfony/Component/Locale/Resources/stubs/var.php ...../symfony/src/Symfony/Component/Locale/Resources/stubs/author.php That's also a performance killer :), have you noticed that one? Thanks, On May 9, 12:43 pm, Christophe COEVOET <[email protected]> wrote: > Le 09/05/2011 11:35, Mauricio Morales a crit : > > > > > > > > > Thanks Lukas, > > > We are not using proxy autogeneration. I'm generating both proxies and > > hydrators and autogeneration is disabled via config. This is the > > config we're using: > > > doctrine_mongo_db: > > default_database: poc_db > > connections: > > default: > > server: mongodb://mongo:27017 > > options: > > connect: true > > document_managers: > > default: > > mappings: > > WebsiteBundle: { type: annotation, dir: "%kernel.root_dir > > %/../src/App/Domain/Document", prefix: App\Domain\Document } > > metadata_cache_driver: array > > using an ArrayCache for the metadata means that they are only cached for > the current request. you should use APC or Memcache in prod to increase > the performances. > > -- > Christophe | Stof -- If you want to report a vulnerability issue on symfony, please send it to security at symfony-project.com You received this message because you are subscribed to the Google Groups "symfony developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/symfony-devs?hl=en
