Performance statistics

[gribber]

Describe the enhancement

I would like to be able to enable some kind of performance statistics for templates, to show statistics like

• created/triggered events
• number of times triggered / how often triggered
• amount of sensors/domains related
• time spent running

All this to track down performance issues, templates that is very resource intensive

Recently found myself in the situation trying to track down what was causing issues, integrations like Profiler showed lots of events but the events itself wasn't the problem, but a template that triggered on those.
At least in my view, it was kind of hard to find the actual cause was a template triggered on too many events

Example usage

Just a checkbox to enable and a statistics page somewhere

Current workarounds

Disable them one by one and monitor cpu usage.

disadvantages with this is

• it takes time if there is lots of templates
• hard to track down if it's a group of templates
• if templates are dependent on each other, it could be hard to find the actual cause

Anything else?

example of template that in my case caused performance issues
gribber/ha@73c2a49

[Petro31]

All of this can already be done in the template engine or a template entity, including getting history through a service call.

[gribber]

And by that, you mean it's easily implemented or the available options are good enough?
Not sure what service call you talking about, didn't find anything relevant, might very well have missed it as I'm not sure what it's called

Either way, I think there is a user case where it can be very useful, where one can, a little more easily find misbehaving or resource intensive parts (actually not limited to templates either, but that was my primary idea)

regards

[Petro31]

You added the feature request to the template engine, meaning it's something that would be available inside templates. Maybe this wasn't your intention, however that's how it's categorized. And I'm replying based on that foundation.

[gribber]

Ah ok, maybe I misunderstood the categories and misplaced it, might fit better in "Core functionality" then I guess, sorry for that!