tag:support.nodebox.net,2012-11-01:/discussions/general-discussion/15012-show-timing-visuallyNodeBox: Discussion 2019-12-15T02:12:52Ztag:support.nodebox.net,2012-11-01:Comment/479054962019-12-09T13:36:50Z2019-12-09T13:36:50ZShow Timing Visually!<div><p>This is really cool! I would love to add this to get more insight into what the app is doing.</p>
<p>Some node-based applications already do this node coloring; e.g. see the screenshot about Nuke performance on <a href="https://learn.foundry.com/nuke/content/comp_environment/organizing_scripts/using_performance_timingscript_profiling.html">this page</a>.</p>
<p>The performance impact of measuring performance impact (noting the begin/end time stamp of each node) would be negligible.</p>
<p>There has also been some work on doing this for text-based languages as well. E.g. Chrome's JavaScript profiler can show how much time each line of code takes, visually: <a href="https://developers.google.com/web/tools/chrome-devtools/evaluate-performance/imgs/forced-layout-src.png">https://developers.google.com/web/tools/chrome-devtools/evaluate-pe...</a> (from this page: <a href="https://developers.google.com/web/tools/chrome-devtools/evaluate-performance/">https://developers.google.com/web/tools/chrome-devtools/evaluate-pe...</a>)</p>
<p>In general we could do simple node-by-node measuring. Things become a bit more complex for subnetworks, where you might want to visualize the total impact of the subnetwork, given that it can be ran multiple times using list matching.</p></div>Frederik De Blesertag:support.nodebox.net,2012-11-01:Comment/479054962019-12-15T02:12:51Z2019-12-15T02:12:51ZShow Timing Visually!<div><p>Seems like a nice holiday project!</p>
<p>If you need any help or suggestions for other ways to improve our code visualization, let me know!</p>
<p>John</p></div>john