Confirmed users
83
edits
DevTools/Planning/Performance/Details: Difference between revisions
DevTools/Planning/Performance/Details (view source)
Revision as of 23:17, 22 November 2013
, 22 November 2013→Product Design Patterns
| Line 55: | Line 55: | ||
'''3) One single recording tool as opposed to distinct recording tools'''<br> | '''3) One single recording tool as opposed to distinct recording tools'''<br> | ||
Does a developer really need to figure out whether to do a "timeline" or a "CPU profile" or a "whatever profile?". Isn't it enough to have one recording UI that provides a container for any "type" of recording? In reality, there is only one recording but with different depths of instrumentation. This does pose a challenge: how to have a combined temporal and memory based view. My gut tells me this is doable, we will just need to find an easy, user friendly way of doing it. | Does a developer really need to figure out whether to do a "timeline" or a "CPU profile" or a "whatever profile?". Isn't it enough to have one recording UI that provides a container for any "type" of recording? In reality, there is only one recording but with different depths of instrumentation. This does pose a challenge: how to have a combined temporal and memory based view. My gut tells me this is doable, we will just need to find an easy, user friendly way of doing it. | ||
<ul> | |||
<li>Timeline layers is one way to give us the ability to correlate different timelines on top of each other. | |||
<li>Each layer can be turned on or off and it would turn on or off the respective instrumentation. | |||
</li> | |||
'''4) Changing sampling/instrumentation depth'''<br> | '''4) Changing sampling/instrumentation depth'''<br> | ||