[WIP] Added simple time tracking panel

[stekycz]

Shows all timer results in time panel for easier time debugging. See http://forum.nette.org/cs/21752-vysledky-mereni-casu-v-debbuger-baru

Questions

• Default listener for logging times of Application and Presenter should be in application I guess, right? Not related, see [WIP] Added simple time tracking panel #91 (comment)
• Should disable option exist in NEON configuration (using CompilerExtension)?
• What about time panel ID? Is it ok to name it as I did or should I use generated name in method addPanel as ID to get the panel?
• Are all used information needed in table?
• Is there some way (or should be) to create some "tree" of times? For example Application::onStartup could be collapsed hiding all times generated during this event (in all its listeners).

[JanTvrdik]

I don't see a point in built-in measuring Application or Presenter. It will tell you nothing useful.

[stekycz]

I think it will. There is a lot of things you can measure - action, handles, beforeRender, render, afterRender, shutdown etc. It could tell in which part of the application life cycle could be a bottle neck.

It is also taken from mentioned topic, see http://forum.nette.org/cs/21752-vysledky-mereni-casu-v-debbuger-baru#p148559

[JanTvrdik]

@stekycz You should use a profiler for this. Measuring it with Tracy will slow down application and provide very little of actually useful data.

[stekycz]

@JanTvrdik Yes, I use profiles when it is needed. I probably understand what you mean. This feature is probably for extra extension only for those who would like to use it.

[JanTvrdik]

You should probably use __CLASS__ . ':time' here.

[stekycz]

Yes, it could be better. I could also use default logic without need of own ID. However I am not sure what is better.

[JanTvrdik]

Custom ID is better.

[JanTvrdik]

Is there some way (or should be) to create some "tree" of times?

That would be cool, however it is not possible because the calls may look like this:

Debugger::timer('a');
Debugger::timer('b');
Debugger::timer('b');
Debugger::timer('b');
Debugger::timer('c');
Debugger::timer('a');
Debugger::timer('c');

I see no way how to render tree from this.

[stekycz]

There could be some optional parameter with meaning of depth. If not specified it takes current internal depth. For example:

Debugger::timer('a', -1);
Debugger::timer('b');
Debugger::timer('b');
Debugger::timer('b');
Debugger::timer('c');
Debugger::timer('a', +1);
Debugger::timer('c');

[fprochazka]

I'd suggest finishing the current implementation first. Improvements can be done separately :)

[JanTvrdik]

There could be some optional parameter with meaning of depth.

No, there really could not be some magical optional parameter which nobody would use.

---

The biggest problem with the current implementation (assuming all may suggestions are accepted) is that the last two columns have confusing names. One is "since last" and the other is "since last with same name" but named just "delta". But "since last" is also a delta. I have no idea for better column names however.

[dg]

Panel time was removed, but this can be nice extension.

[stekycz]

@dg Do you mean extra extension or extension included in Nette? Current implementation (without time panel) could be updated to use this idea.

[dg]

It is developed and maintained by you, so your extension.

[stekycz]

Understood

[dg]

When it will be mature and will prove that it is useful and you will be willing to do it, we can merge it to Tracy.

[stekycz]

We will see :-)