Tom: While a dashboard showing length of time PRD's are running is interesting and useful, what I think the request here is more focused on processes inside the PRD.

That is, if you design a complex PRD, what activities are taking the most time to process? Debugging the PRD itself, in terms of performance. 

In NDStrace you could (I wish you would!!!) offer a tool that looks at timestamps and finds the hotspots, where the time gap between lines is largest.  (I have been bugging Stefaan to add this to his Advanced DS Trace plugin, but he has not done it).  So in the engine context the example woould be, isolate one event, and find the longest pauses between trace lines. What is slowest?

Similarly for the Activities in the Workflow, which ones take the longest time.

Tom: While a dashboard showing length of time PRD's are running is interesting and useful, what I think the request here is more focused on processes inside the PRD.

That is, if you design a complex PRD, what activities are taking the most time to process? Debugging the PRD itself, in terms of performance. 

In NDStrace you could (I wish you would!!!) offer a tool that looks at timestamps and finds the hotspots, where the time gap between lines is largest.  (I have been bugging Stefaan to add this to his Advanced DS Trace plugin, but he has not done it).  So in the engine context the example woould be, isolate one event, and find the longest pauses between trace lines. What is slowest?

Similarly for the Activities in the Workflow, which ones take the longest time.