you get cache slam problems also, i think bytecode caches handle many different files just well.
On Wed, 2 Feb 2011 22:11:48 +0100 Lukas Kahwe Smith <[email protected]> wrote: > > On 02.02.2011, at 22:05, Johannes wrote: > > > I'm not sure if this was investigated at some point, but since the DIC > > allows us to determine the dependencies between the different services > > easily, we could compile the class/interface files for all dependent > > services/classes into one file and load this one file before a service > > is instantiated. > > > > Since I haven't done any tests, I don't know how much we could gain by > > this, but it would certainly save some round trips via the auto-loader. > > > I dont think its really worth it. > You mostly gain performance for people not using a byte code cache. > For those using byte code caches you save on disc i/o in case they do not > disable file stating to detect file changes. > > But it gets pretty tricky to handle this in case a dependency is used in a > few different permutations. > > So overall the best approach is to define sort of the lowest common > denominator for all requests and compile that into a single file that is > always loaded and not bother with anything else. > > regards, > Lukas Kahwe Smith > [email protected] > > > > -- > 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 > -- 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
