Hi François,
Thanks for the detailed reply. I knew Id seen these times before but I was still learning symfony back then and nowhere near optimizing. How about enabling this timing information as a config option? I understand that time spent in the core cannot be optimized. Nevertheless, find that timing information could really help in debugging within actions and templates as db queries and custom inserted log messages make good and easy marks for identifying those parts that might need optimizing. Gert. From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Francois Zaninotto Sent: woensdag 9 mei 2007 9:41 To: [email protected] Subject: [symfony-devs] Re: detailed timing in debug bar Gert, What you ask used to be the case of the web debug toolbar before r1936. The displayed times were not understood, and that's why we decided to display only the timers that users can optimize, i.e. the time consumed in the application code, and not the timers they can not optimize, i.e. the time consumed in the framework code. The timers data already give a good clue of where you should start optimizing, and you can add timers of your own to figure out the best place to start. Besides, we used to display the time elapsed between two events in the 'logs & msgs' panel, and that was not corresponding to the time necessary to achieve the corresponding part of code. The information was confusing, so it was removed. If you want to test the way the toolbar used before, you can always checkout the r1935 code. François _____ De : [email protected] [mailto:[EMAIL PROTECTED] De la part de Gert Vrebos - Tactics bvba Envoyé : mardi 8 mai 2007 21:13 À : [email protected] Objet : [symfony-devs] detailed timing in debug bar Hi all, I believe it would be an easy but valuable addition to logs&msgs in the web debug toolbar to display total elapsed time since the request start (and/or time since previous message). This could make performance optimizing so much easier as one can much faster identify the time consuming parts of code. The provided totals are usefull but do not help here. I know there are sfTimers but these need to be explicitly inserted, ie tedious debugging. Anybody second this? I would like to create a ticket Cheers Gert. <BR --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
