call_dynamic is used solely to implement <%shared> sections. If you find a way to do without the <%shared> sections, the call_dynamic should disappear. Whether you should bother depends not on how many call_dynamic calls there are, but how expensive they are according to a profile. Have you profiled?
Jon On Apr 2, 2009, at 8:13 AM, Jérôme Etévé wrote: > Hi everyone, > > I'm fighting here with a problem about a large number of > Mason::Request::call_dynamic in my application. > > By any chance, is the number of 'paths' mason has to search for > components in can be related to the number of calls to call_dynamics ? > > For instance, I have a mason server with 4 component paths: > > beta/ > generic/ > htdocs_beta/ > htdocs/ > > And the number of call to 'Mason::Request::call_dynamic' on it > (2004) is exactly twice the number of calls to > 'Mason::Request::call_next' (1002) > > > On the other hand, I have a standard server with only 2 component > paths > generic/ > htdocs/ > > The number of Mason::Request::call_next is exactly the same (1002) - > thx to the test set being the same, but the number of call_dynamic is > only 1670. > > Are those numbers related in any way? Can the number of component > path influence the number of call_dynamic being made? > > Thanks for your help ! > > Jerome. > > Ps: profiling made with NYTProf > > > -- > Jerome Eteve. > > Chat with me live at http://www.eteve.net > > [email protected] > > ------------------------------------------------------------------------------ > _______________________________________________ > Mason-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/mason-users ------------------------------------------------------------------------------ _______________________________________________ Mason-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mason-users
