<?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 FFT performance issue in Intel® oneAPI Math Kernel Library</title>
    <link>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/FFT-performance-issue/m-p/1179761#M29244</link>
    <description>&lt;P&gt;I am evaluating the MKL library for the new project. While computing the FFT, I could see that performance of the FFT (in terms of GFLOP/s) reduces if the threads are in different socket ( using thread affinity). The test was carried out in Intel(R) Xeon(R) CPU E5-2650 processor and compiler is gcc. Please let me know the reason.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Sat, 05 May 2018 06:41:17 GMT</pubDate>
    <dc:creator>c__vishnu</dc:creator>
    <dc:date>2018-05-05T06:41:17Z</dc:date>
    <item>
      <title>FFT performance issue</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/FFT-performance-issue/m-p/1179761#M29244</link>
      <description>&lt;P&gt;I am evaluating the MKL library for the new project. While computing the FFT, I could see that performance of the FFT (in terms of GFLOP/s) reduces if the threads are in different socket ( using thread affinity). The test was carried out in Intel(R) Xeon(R) CPU E5-2650 processor and compiler is gcc. Please let me know the reason.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 05 May 2018 06:41:17 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/FFT-performance-issue/m-p/1179761#M29244</guid>
      <dc:creator>c__vishnu</dc:creator>
      <dc:date>2018-05-05T06:41:17Z</dc:date>
    </item>
    <item>
      <title>Hi Vishnu,</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/FFT-performance-issue/m-p/1179762#M29245</link>
      <description>&lt;P&gt;Hi Vishnu,&lt;BR /&gt;
	&lt;BR /&gt;
	​The first thought&amp;nbsp;, it is threading and memory localization problem.&amp;nbsp; The current CPU&amp;nbsp;and memory structure&amp;nbsp;expected&amp;nbsp;the threads have access to&amp;nbsp;their data as near as possible.&amp;nbsp; It may not only about MKL FFT, it should be any mulitithreaded computation task.&amp;nbsp; How do store the FFT data and affinity the thread to different sockets?&lt;/P&gt;

&lt;P&gt;And MKL developer guide &lt;A href="https://software.intel.com/en-us/mkl-linux-developer-guide-managing-multi-core-performance" target="_blank"&gt;https://software.intel.com/en-us/mkl-linux-developer-guide-managing-multi-core-performance&lt;/A&gt; have some discussed about how to get best performance by thread affinity.&amp;nbsp; for your reference.&lt;/P&gt;

&lt;P&gt;You can obtain best performance on systems with multi-core processors by requiring that threads do not migrate from core to core. ​&lt;/P&gt;

&lt;P&gt;Best Regards,&lt;/P&gt;

&lt;P&gt;​Ying&lt;/P&gt;

&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 08 May 2018 06:28:18 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/FFT-performance-issue/m-p/1179762#M29245</guid>
      <dc:creator>Ying_H_Intel</dc:creator>
      <dc:date>2018-05-08T06:28:18Z</dc:date>
    </item>
  </channel>
</rss>

