<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><br><div><div>On 22 May 2017, at 21:35, Steven R. Brandt <<a href="mailto:sbrandt@cct.lsu.edu">sbrandt@cct.lsu.edu</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">Is there a way to graphically display cactus timer data? We're thinking <br>about having an REU student develop such a tool if it doesn't exist. Thanks.<br></blockquote><div><br></div><div>Hi Steve,</div><div><br></div><div>Not that I know of. What sort of graphical display are you thinking of? Anyone can plot the Carpet timing variables (physical_time_per_hour as a function of time) etc in whatever they usually use to make plots of Cactus data.</div><div><br></div><div>If you are thinking of the detailed timers used to profile the different parts of the code, then it would be good to have something to make a quick plot of these. They could take the timertree.*.xml files and produce a hierarchical display of the timers. This could be a tree or a pie chart. I have done this before using Mathematica. Some of the things I did were:</div><div><br></div><div><span class="Apple-tab-span" style="white-space:pre"> </span>– Selecting a threshold so that timers which contribute a small amount are omitted, otherwise there are too many timers to display</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>– Creating "groups" (via string patterns) so that you can logically group things together (e.g. you might want to merge all the different McLachlan RHS timers into a single one) depending on the analysis you are doing</div><div><br></div><div>It would be good to have a tool, maybe based on Python and Matplotlib, to generate such plots quickly and simply. One issue is that the timer XML files are only written at the end of the simulation, and their content is not reduced among processors. It is usually quite important to consider all the processors, not just the first one, so we should think about how this should be done. Depending on what you want to achieve, it could also be useful to output the XML files regularly, though then you have to think about whether it's important to keep the historical data, or just replace with the current totals. It also leads to a large number of output files since we have one per process. This is why I don't enable this timer output in my own simulations, except when explicitly benchmarking/profiling. </div><div><br></div><div>Perhaps you could create a page under "projects" on the ET wiki and we can make notes and suggestions there?</div></div><br><div apple-content-edited="true">
<div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div>-- </div><div>Ian Hinder</div><div><a href="http://members.aei.mpg.de/ianhin">http://members.aei.mpg.de/ianhin</a></div></div></div></div></div>
</div>
<br></body></html>