<?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 Re: profiling with time limit in Intel® MPI Library</title>
    <link>https://community.intel.com/t5/Intel-MPI-Library/profiling-with-time-limit/m-p/1365780#M9255</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks for reaching out to us.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;&lt;FONT color="#808080"&gt;&amp;gt;&amp;gt;"How can i achieve this using aps? are there any additional options to make profiler stop gathering data?"&lt;/FONT&gt;&lt;/EM&gt;&lt;/P&gt;
&lt;OL&gt;
&lt;LI&gt;Application Performance Snapshot supports the region control with the MPI_Pcontrol() operation.&amp;nbsp;&lt;/LI&gt;
&lt;LI&gt;This allows you to enable and disable statistics collection for specific application regions in the source code. Region control only affects MPI and OpenMP* metrics, while the other ones will still be collected for the entire application.&amp;nbsp;&lt;/LI&gt;
&lt;/OL&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;For more information refer to the below link:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.intel.com/content/www/us/en/develop/documentation/application-snapshot-user-guide/top/detailed-analyses/mpi-analyses/region-control-with-mpi-pcontrol.html" target="_blank" rel="noopener"&gt;https://www.intel.com/content/www/us/en/develop/documentation/application-snapshot-user-guide/top/detailed-analyses/mpi-analyses/region-control-with-mpi-pcontrol.html&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;FONT color="#808080"&gt;&lt;I&gt;&amp;gt;&amp;gt;" if i kill the application.exe after 50 minutes, the profiler will be able to show correct data?"&lt;/I&gt;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;No, It is not recommended to kill an application as it may result in either incorrect data or no data.&amp;nbsp;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks &amp;amp; Regards,&lt;/P&gt;
&lt;P&gt;Santosh&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 04 Mar 2022 09:48:34 GMT</pubDate>
    <dc:creator>SantoshY_Intel</dc:creator>
    <dc:date>2022-03-04T09:48:34Z</dc:date>
    <item>
      <title>profiling with time limit</title>
      <link>https://community.intel.com/t5/Intel-MPI-Library/profiling-with-time-limit/m-p/1365462#M9246</link>
      <description>&lt;P&gt;Hi,&amp;nbsp;&lt;BR /&gt;I have a simulation setup which has been compiled with intel 2020u4.&lt;/P&gt;
&lt;P&gt;problem statement -&amp;nbsp;&lt;BR /&gt;The setup has 2 parts - input read, output writing.&lt;BR /&gt;scenario a) When i run a single copy of my setup, everything works fine, i.e. input read completes in ~20 minutes and output writing phase in ~60 minutes (overall ~80 minutes)&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;scenario b) But when i run multiple copies of the same run, then the input phase takes ~50 minutes followed by ~60 minutes of output .&lt;BR /&gt;&lt;BR /&gt;I plan to use intel profiler to find the "slowest part" with the runs. I plan to run the profiler in scenario a) but i plan to profile only initial 50 minutes of simulation, and i dont care about the "output phase" profiling data.&lt;BR /&gt;How can i achieve this using aps?&lt;BR /&gt;&lt;BR /&gt;i understand that the mpirun command will be -&amp;nbsp;&lt;BR /&gt;mpirun -np X -ppn Y aps --collection-mode=mpi ./application.exe&lt;BR /&gt;&lt;BR /&gt;But are there any additional options to make profiler stop gathering data?&lt;BR /&gt;or if i kill the application.exe after 50 minutes, the profiler will be able to show correct data?&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 03 Mar 2022 10:01:31 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-MPI-Library/profiling-with-time-limit/m-p/1365462#M9246</guid>
      <dc:creator>psing51</dc:creator>
      <dc:date>2022-03-03T10:01:31Z</dc:date>
    </item>
    <item>
      <title>Re: profiling with time limit</title>
      <link>https://community.intel.com/t5/Intel-MPI-Library/profiling-with-time-limit/m-p/1365780#M9255</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks for reaching out to us.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;EM&gt;&lt;FONT color="#808080"&gt;&amp;gt;&amp;gt;"How can i achieve this using aps? are there any additional options to make profiler stop gathering data?"&lt;/FONT&gt;&lt;/EM&gt;&lt;/P&gt;
&lt;OL&gt;
&lt;LI&gt;Application Performance Snapshot supports the region control with the MPI_Pcontrol() operation.&amp;nbsp;&lt;/LI&gt;
&lt;LI&gt;This allows you to enable and disable statistics collection for specific application regions in the source code. Region control only affects MPI and OpenMP* metrics, while the other ones will still be collected for the entire application.&amp;nbsp;&lt;/LI&gt;
&lt;/OL&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;For more information refer to the below link:&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.intel.com/content/www/us/en/develop/documentation/application-snapshot-user-guide/top/detailed-analyses/mpi-analyses/region-control-with-mpi-pcontrol.html" target="_blank" rel="noopener"&gt;https://www.intel.com/content/www/us/en/develop/documentation/application-snapshot-user-guide/top/detailed-analyses/mpi-analyses/region-control-with-mpi-pcontrol.html&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;FONT color="#808080"&gt;&lt;I&gt;&amp;gt;&amp;gt;" if i kill the application.exe after 50 minutes, the profiler will be able to show correct data?"&lt;/I&gt;&lt;/FONT&gt;&lt;/P&gt;
&lt;P&gt;No, It is not recommended to kill an application as it may result in either incorrect data or no data.&amp;nbsp;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thanks &amp;amp; Regards,&lt;/P&gt;
&lt;P&gt;Santosh&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 04 Mar 2022 09:48:34 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-MPI-Library/profiling-with-time-limit/m-p/1365780#M9255</guid>
      <dc:creator>SantoshY_Intel</dc:creator>
      <dc:date>2022-03-04T09:48:34Z</dc:date>
    </item>
    <item>
      <title>Re:profiling with time limit</title>
      <link>https://community.intel.com/t5/Intel-MPI-Library/profiling-with-time-limit/m-p/1367862#M9294</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;We haven't heard back from you. Could you please provide an update on your issue?&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Thanks &amp;amp; Regards,&lt;/P&gt;&lt;P&gt;Santosh&lt;/P&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 11 Mar 2022 05:48:15 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-MPI-Library/profiling-with-time-limit/m-p/1367862#M9294</guid>
      <dc:creator>SantoshY_Intel</dc:creator>
      <dc:date>2022-03-11T05:48:15Z</dc:date>
    </item>
    <item>
      <title>Re:profiling with time limit</title>
      <link>https://community.intel.com/t5/Intel-MPI-Library/profiling-with-time-limit/m-p/1369945#M9332</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;I assume that your issue is resolved. If you need any additional information, please post a new question as this thread will no longer be monitored by Intel.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Thanks &amp;amp; Regards,&lt;/P&gt;&lt;P&gt;Santosh&lt;/P&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 18 Mar 2022 05:20:53 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-MPI-Library/profiling-with-time-limit/m-p/1369945#M9332</guid>
      <dc:creator>SantoshY_Intel</dc:creator>
      <dc:date>2022-03-18T05:20:53Z</dc:date>
    </item>
  </channel>
</rss>

