Some performance problems (quite a few, actually) don’t show up on a simple time consumed chart. Maybe we can add new reporting options to expand the class of performance problems we can help identify.

Here are a couple options I can think of:

• FICO-style score that emphasizes spikes in cpu time consumed within a small window of real time
  • This is the idea behind metrics like TMI, by the way.
• Detect and log when a trigger marks a state as changed, when there is no detectable change.
  • How would we do this? The states are unfortunately used as mutable objects. Perhaps we would do a shallow clone on each state (via Mixin), and then compare the states after. Definitely a more cpu intensive metric to be enabled on a case-by-case basis.

it's a good 3 years since i wrote this ticket, and im pretty sure this is a silly idea and we don't need to keep it open in the issue tracker. the number of people who would be able to actually understand a FICO style score is probably less than 10. As for the other suggestion, i don't think there's ever a situation where some judicious DebugPrints wouldn't solve the same problem.