What I call "rendering templates" is only the view part of the MVC model. Waiting for XML and reading them is definitly between Model (beans) and Controler (actions and readers). But our templates are a bit complex : depending on the offer size, we have 12 different main templates to render an offer. And for each one, we need about 10 partials to render some common field on our offers.
I will have a closer look tomorrow at the "project:optimize" task. It could be usefull even if IO does not seem to be the bottleneck (we monitor them with some Nagios scripts and IO are not an issue for the moment). About the routing we are using it, using it a lot in fact ! But I've added a timer inside the "url_for" method and it does not cost anything at all. We already made the choice to reference routes by Id and not module/action so it prevents Symfony to perform useless array searches. We don't share session across servers : we only save a few information inside cookies and we try to have as few cookie as possible since they are consuming some bandwidth and, so, some performances for our customer. We are basically working with only two cookies : one for storing an uniqueId (very usefull for statistics) and the other to track the traffic source (SEO, SEM, spontaneous, partnership, ...). We did the choice to be sessionless to avoid having to deal with sharing sessions between servers (ort even datacenters) : it's costly and often hard to maintain (even with a session warehouse). Thanks again ! I think my next moves will be to : test XHProf, refine my timer usage to track closely what happened in some costly algorithms (like templates) and, finally, contact Sensio to discuss about having an expert working with us for a few days. But I'll let this last part to my CTO :) Rémi On 17 nov, 16:30, pghoratiu <pghora...@gmail.com> wrote: > > In the meantime, we have moved forward on our timer method and we > > discovered that rendering templates took us about 200ms. Don't you > > think this is huge ? > > Thanks anyway ! > > ===== > Does this include the time to wait for the XML data source? > > On my dev machine it takes about 17 ms to process factories, 6 ms for > configuration so about 23 ms of overhead is always present. > For a simple page that is constructed by 5 db accesses it takes aprox. > 5 ms to process the action and 65 ms to render the view and 100 ms to > render > the rest of the layout, components on the page, in total about 193 ms. > I think that 200 ms can be large but again depends on what code do you > have in the view. > > Check out also this optimization flag, I did not try out myself, maybe > it helps > you:http://www.symfony-project.org/tutorial/1_4/en/whats-new#chapter_a2fa... > > You did not say anything about the routing, if you use it or not? > How do you share session information across machines? > > I'm curious what you'll find to be the bottleneck :) > > gabriel -- 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 users" group. To post to this group, send email to symfony-users@googlegroups.com To unsubscribe from this group, send email to symfony-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en
