<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Well, Bernard, you haven't in Intel® Moderncode for Parallel Architectures</title>
    <link>https://community.intel.com/t5/Intel-Moderncode-for-Parallel/runtime-of-functions/m-p/952962#M5218</link>
    <description>&lt;P&gt;Well, Bernard, you haven't mentioned that this is a non-mpi function. It doesn't have statistics information in the trace.&lt;/P&gt;
&lt;P&gt;So, you should generate a text representation of the trace `xstftool sofi3D.stf &amp;gt; sofi3D.avt`&lt;BR /&gt;After that `grep exchange_s sofi3d.avt`.&lt;/P&gt;
&lt;P&gt;I'm not familiar with user code investigation by ITAC but I hope that looking at the AVT file may give you a clue - just open it in a text viewer.&lt;/P&gt;
&lt;P&gt;Yeah, 3e-5 is rather rounding error because each event has precision&amp;nbsp;worse than&amp;nbsp;1e-6.&lt;/P&gt;
&lt;P&gt;Regards!&lt;BR /&gt;---Dmitry&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 19 Jul 2013 07:32:22 GMT</pubDate>
    <dc:creator>Dmitry_K_Intel2</dc:creator>
    <dc:date>2013-07-19T07:32:22Z</dc:date>
    <item>
      <title>runtime of functions</title>
      <link>https://community.intel.com/t5/Intel-Moderncode-for-Parallel/runtime-of-functions/m-p/952960#M5216</link>
      <description>&lt;P&gt;Hello!&lt;/P&gt;
&lt;P&gt;I've got a question concerning the Comand Line Interface of Intel trace Analyzer. I want to evaluate the total-runtime of one function of a mpi-program. I know how to do this using the GUI, but I want to get the average runtime of about 20 runs of the MPI-program. So how can I "ungroup" (as it is called in the GUI-version) the functions in the CLI? At the moment I can only find out how long the programm in total was running...&lt;/P&gt;
&lt;P&gt;Thank you in advance for an answer&lt;/P&gt;
&lt;P&gt;Bernhard&lt;/P&gt;</description>
      <pubDate>Wed, 17 Jul 2013 15:58:27 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Moderncode-for-Parallel/runtime-of-functions/m-p/952960#M5216</guid>
      <dc:creator>Bernhard</dc:creator>
      <dc:date>2013-07-17T15:58:27Z</dc:date>
    </item>
    <item>
      <title>Hi Bernard,</title>
      <link>https://community.intel.com/t5/Intel-Moderncode-for-Parallel/runtime-of-functions/m-p/952961#M5217</link>
      <description>&lt;P&gt;Hi Bernard,&lt;/P&gt;
&lt;P&gt;Looks like stftool (a part of ITAC package) could help you. You can use:&lt;BR /&gt;&amp;nbsp;&amp;nbsp; stftool trace_name.stf --print-statistics&amp;nbsp; &amp;gt;trace_name.stats&lt;/P&gt;
&lt;P&gt;This command generates summary information about all commands.&lt;BR /&gt;But, you need to get information about one tick duration and it means that you need to convert a trace and get CLKPERIOD value. You may use:&lt;BR /&gt;&amp;nbsp;&amp;nbsp; xstftool trace_name.stf --print-statistics | grep CLKPERIOD&lt;/P&gt;
&lt;P&gt;To get function index you may need to use:&lt;BR /&gt;&amp;nbsp;&amp;nbsp; xstftool trace_name.stf --print-statistics | grep MPI_Alltoall&lt;/P&gt;
&lt;P&gt;After that just try this out:&lt;BR /&gt;&amp;nbsp;&amp;nbsp; grep " N:" trace_name.stats&lt;BR /&gt;where N is the index you got by the previous command (number after DEFSTATE)&lt;/P&gt;
&lt;P&gt;Sure, you can use `xstftool trace_name.stf`which genereates human readable text file and you can easily parse it but be prepared that it may take a lot of time to generate output file and it may be huge.&lt;/P&gt;
&lt;P&gt;Regards!&lt;BR /&gt;---Dmitry&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 18 Jul 2013 08:28:11 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Moderncode-for-Parallel/runtime-of-functions/m-p/952961#M5217</guid>
      <dc:creator>Dmitry_K_Intel2</dc:creator>
      <dc:date>2013-07-18T08:28:11Z</dc:date>
    </item>
    <item>
      <title>Well, Bernard, you haven't</title>
      <link>https://community.intel.com/t5/Intel-Moderncode-for-Parallel/runtime-of-functions/m-p/952962#M5218</link>
      <description>&lt;P&gt;Well, Bernard, you haven't mentioned that this is a non-mpi function. It doesn't have statistics information in the trace.&lt;/P&gt;
&lt;P&gt;So, you should generate a text representation of the trace `xstftool sofi3D.stf &amp;gt; sofi3D.avt`&lt;BR /&gt;After that `grep exchange_s sofi3d.avt`.&lt;/P&gt;
&lt;P&gt;I'm not familiar with user code investigation by ITAC but I hope that looking at the AVT file may give you a clue - just open it in a text viewer.&lt;/P&gt;
&lt;P&gt;Yeah, 3e-5 is rather rounding error because each event has precision&amp;nbsp;worse than&amp;nbsp;1e-6.&lt;/P&gt;
&lt;P&gt;Regards!&lt;BR /&gt;---Dmitry&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 19 Jul 2013 07:32:22 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Moderncode-for-Parallel/runtime-of-functions/m-p/952962#M5218</guid>
      <dc:creator>Dmitry_K_Intel2</dc:creator>
      <dc:date>2013-07-19T07:32:22Z</dc:date>
    </item>
    <item>
      <title>BTW, Bernhard,Intel MPI has</title>
      <link>https://community.intel.com/t5/Intel-Moderncode-for-Parallel/runtime-of-functions/m-p/952963#M5219</link>
      <description>&lt;P&gt;BTW, Bernhard,&lt;BR /&gt;Intel MPI has internal statistics. Just set I_MPI_STATS to a value from 1 to 10 and you can get some information (might be very difficult to ananlyze automatically). And there is 'ipm' value to produce an output in IPM-like format. Just give it a try and might you'll find it useful.&lt;/P&gt;
&lt;P&gt;Regards!&lt;BR /&gt;---Dmitry&lt;/P&gt;</description>
      <pubDate>Mon, 22 Jul 2013 07:30:24 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Moderncode-for-Parallel/runtime-of-functions/m-p/952963#M5219</guid>
      <dc:creator>Dmitry_K_Intel2</dc:creator>
      <dc:date>2013-07-22T07:30:24Z</dc:date>
    </item>
  </channel>
</rss>

