<?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 Best Time routine/function for benchmark  timing tests? in Intel® Fortran Compiler</title>
    <link>https://community.intel.com/t5/Intel-Fortran-Compiler/Best-Time-routine-function-for-benchmark-timing-tests/m-p/812554#M43596</link>
    <description>I have used the Window timer functions several time. Maybe the attached files helps you, incaseyou want to go that way!&lt;BR /&gt;Robert&lt;BR /&gt;</description>
    <pubDate>Fri, 04 Feb 2011 14:41:00 GMT</pubDate>
    <dc:creator>Robert_van_Amerongen</dc:creator>
    <dc:date>2011-02-04T14:41:00Z</dc:date>
    <item>
      <title>Best Time routine/function for benchmark  timing tests?</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/Best-Time-routine-function-for-benchmark-timing-tests/m-p/812550#M43592</link>
      <description>I have tried calling CPU_TIME(T) before and after code and got zero difference on frequent occasions. I could expect this if there is more than one cpu and the timer gets time from one of them only. When you have a multi-core CPU, what is the best way to get correct timing information about code execution that may be parallelised to run on more than one cpu using xmm registers?</description>
      <pubDate>Mon, 31 Jan 2011 09:48:55 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/Best-Time-routine-function-for-benchmark-timing-tests/m-p/812550#M43592</guid>
      <dc:creator>anthonyrichards</dc:creator>
      <dc:date>2011-01-31T09:48:55Z</dc:date>
    </item>
    <item>
      <title>Best Time routine/function for benchmark  timing tests?</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/Best-Time-routine-function-for-benchmark-timing-tests/m-p/812551#M43593</link>
      <description>cpu_time usually has a resolution of 0.01 seconds, so will be unable to resolve smaller time intervals. When running multiple threads on any current OS, cpu_time attempts to add up the time spent by all threads on the associated process. You don't normally expect to reduce the total cpu time of all threads; usually you are interested in overall elapsed time. Only on Win9x did cpu_time measure elapsed time.&lt;BR /&gt;As Windows has equally poor resolution in system_clock, you should consider elapsed time timers such as omp_get_wtime, if using OpenMP or auto-parallel. &lt;BR /&gt;Windows performance timers or _rdtsc() may be useful, but require you to make a C wrapper, unless you figure out how to access the Windows timers via USE iso_c_binding. With _rdtsc, in principle, you must assure that you compare times taken only on the same CPU.</description>
      <pubDate>Mon, 31 Jan 2011 13:26:50 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/Best-Time-routine-function-for-benchmark-timing-tests/m-p/812551#M43593</guid>
      <dc:creator>TimP</dc:creator>
      <dc:date>2011-01-31T13:26:50Z</dc:date>
    </item>
    <item>
      <title>Best Time routine/function for benchmark  timing tests?</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/Best-Time-routine-function-for-benchmark-timing-tests/m-p/812552#M43594</link>
      <description>As TimP suggests, using omp_get_wtime can be used even for code that is not parallel, as well as code that is parallelwithout OpenMP. You just have to link in the appropriate OpenMP library (easiest way is to declare program is OpenMP but not use OpenMP parallelization in your code). Of course, if your program is already using OpenMP, there is nothing to doother than calling the function.&lt;BR /&gt;&lt;BR /&gt;An alternate method is to use the Windows functions QueryPerformanceCounterand QueryPerformanceCounterFrequency. These functions are available to IVF (interfaces can be found in the IVF include folder).&lt;BR /&gt;&lt;BR /&gt;Jim Dempsey&lt;BR /&gt;</description>
      <pubDate>Mon, 31 Jan 2011 15:36:37 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/Best-Time-routine-function-for-benchmark-timing-tests/m-p/812552#M43594</guid>
      <dc:creator>jimdempseyatthecove</dc:creator>
      <dc:date>2011-01-31T15:36:37Z</dc:date>
    </item>
    <item>
      <title>Best Time routine/function for benchmark  timing tests?</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/Best-Time-routine-function-for-benchmark-timing-tests/m-p/812553#M43595</link>
      <description>Thanks for the info. I will try the omp routine.</description>
      <pubDate>Tue, 01 Feb 2011 10:58:58 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/Best-Time-routine-function-for-benchmark-timing-tests/m-p/812553#M43595</guid>
      <dc:creator>anthonyrichards</dc:creator>
      <dc:date>2011-02-01T10:58:58Z</dc:date>
    </item>
    <item>
      <title>Best Time routine/function for benchmark  timing tests?</title>
      <link>https://community.intel.com/t5/Intel-Fortran-Compiler/Best-Time-routine-function-for-benchmark-timing-tests/m-p/812554#M43596</link>
      <description>I have used the Window timer functions several time. Maybe the attached files helps you, incaseyou want to go that way!&lt;BR /&gt;Robert&lt;BR /&gt;</description>
      <pubDate>Fri, 04 Feb 2011 14:41:00 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Fortran-Compiler/Best-Time-routine-function-for-benchmark-timing-tests/m-p/812554#M43596</guid>
      <dc:creator>Robert_van_Amerongen</dc:creator>
      <dc:date>2011-02-04T14:41:00Z</dc:date>
    </item>
  </channel>
</rss>

