I was going to spend a bit of time writing a patch that will use the Doctrine cache classes for this over the next few days. I'll keep you updated. Not sure based on his responses if Fabien cares about such a dependency on Doctrine\Common, but if he does then I'll just write the classes instead of adapting to Doctrine.
t On Tue, Sep 28, 2010 at 08:25, Dennis Jacobfeuerborn < [email protected]> wrote: > I wanted to try to implement a simple cache for that but I have no > idea where to hook that class into the framework. > I can see that the getValidator_Mapping_ClassMetadataFactoryService() > function in the helloProdProjectContainer class is missing the second > parameter which would be used to pass the instance of the caching > class that implements CacheInterface but helloProdProjectContainer is > stored in the applications cache folder and generated by Symfony so I > have no clue where I have to make the changes to get my implementation > in there. > > Regards, > Dennis > > On Sep 27, 2:41 pm, Fabien Potencier <fabien.potenc...@symfony- > project.com> wrote: > > On 9/27/10 10:30 AM, Tim Nagel wrote: > > > > > Looks like ClassMetadataFactory is set up for caching but there are no > > > cache classes written for validators yet. > > > Fabien: is there any particular reason the Validator cache code isnt > > > using the Doctrine\Common\Cache classes? > > > > Because no other Symfony component use these Doctrine classes yet; and > > then as the component is far from finished/stable yet, cache is not a > > priority. > > > > Fabien > > > > > Happy to have a stab at writing these. > > > t > > > On Mon, Sep 27, 2010 at 15:26, Tim Nagel <[email protected] > > > <mailto:[email protected]>> wrote: > > > > > It doesnt appear to be possible to provide cache driver options to > > > the AnnotationReader in the AnnotationLoader class. It also seems > > > that the validator doesnt cache the metadata classes once generated > > > (like Doctrine does, at least). > > > So in short, I dont think you can. You can however, enable APC or > > > memcached cache drivers for Doctrine2: > > > doctrine.orm: > > > metadata_cache_driver: apc > > > query_cache_driver: apc > > > result_cache_driver: apc > > > *Note: you'll need to clear your cache when you make changes to > > > entities! Best leave it off unless you're in production.* > > > Replace apc with memcached and you'll have yourself a memcached > > > setup, though there are additional configuration options to > > > configure (host, port, etc) which you can find keys for in the > > > DoctrineBundle/Resources/config directory. > > > t > > > > > On Mon, Sep 27, 2010 at 09:46, Dennis Jacobfeuerborn > > > <[email protected] <mailto:[email protected]>> > wrote: > > > > > From what I can see no caching is used at all. How can I tell > > > Symfony > > > which cache driver it is supposed to use? > > > > > On Sep 25, 5:51 am, Tim Nagel <[email protected] > > > <mailto:[email protected]>> wrote: > > > > Are you running memcached or apc cache drivers for > > > annotations or using the > > > > array cache? Annotations will be parsed every request when > > > using the default > > > > array cache. > > > > > > t > > > > > > On 25/09/2010 1:38 PM, "Dennis Jacobfeuerborn" > > > <[email protected] <mailto:[email protected]>> > > > > wrote: > > > > > > I'm using PR3 and 95% of the request time increase seems to > > > be spent > > > > in the parsing of the annotations. > > > > > > On Sep 24, 3:39 pm, Fabien Potencier > <fabien.potenc...@symfony- > > > > > > project.com <http://project.com/>> wrote: > > > > > If you use a sandbox from before PR3, that's because there > > > was an HTTP > > > > > call ... > > > > > -- > > > If you want to report a vulnerability issue on symfony, please > > > send it to security at symfony-project.com > > > <http://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] <mailto: > [email protected]> > > > To unsubscribe from this group, send email to > > > > > > [email protected]<symfony-devs%[email protected]> > > > > > > <mailto:symfony-devs%[email protected]<symfony-devs%[email protected]> > > > > > For more options, visit this group at > > > http://groups.google.com/group/symfony-devs?hl=en > > > > > -- > > > 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]<symfony-devs%[email protected]> > > > For more options, visit this group at > > >http://groups.google.com/group/symfony-devs?hl=en > > -- > 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]<symfony-devs%[email protected]> > For more options, visit this group at > http://groups.google.com/group/symfony-devs?hl=en > -- 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
