mmc realtime cook info for nodes like executeDAT?

executeDAT does not report cooktime in network if you middle mouse click to view info, but does show up in the performance monitor.

It makes it more difficult to optimize / trouble shoot slow python for example.
Also things like panelExecDAT and paramExecDAT etc seem to behave the same way.

Is there any big reason why this hasn’t been implemented thus far? Seems strange that it’s been missing for so long when other nodes have had cook info and sub children cook info more lately.

A callback isn’t really a ‘cook’, since different callbacks can occur at different times throughout a frame, while a cook generally only happens once a frame. I think another entry in the info popup that shows the total time the script took executing this frame could be useful though. We’ll look into that. Thanks for the suggestion!