<?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:Weird time overhead during first call to DGEQRF and DSYRK in Intel® oneAPI Math Kernel Library</title>
    <link>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/Weird-time-overhead-during-first-call-to-DGEQRF-and-DSYRK/m-p/1679170#M37019</link>
    <description>&lt;P&gt;HI Jacek,&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;When you run this function for the first time, many things happen behind the scenes, so it's normal for it to take longer. For smaller sizes, you can try using direct call or sequential mode (&lt;A href="https://www.intel.com/content/www/us/en/docs/onemkl/developer-guide-linux/2025-1/using-mkl-direct-call-in-c-applications.html" rel="noopener noreferrer" target="_blank"&gt;Using MKL_DIRECT_CALL in C Applications&lt;/A&gt;).&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Also, could you provide us with more context about what your application does and what kind of usage of oneMKL you expect? We can try to find a better solution for your case.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Aleksandra&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;BR /&gt;</description>
    <pubDate>Mon, 31 Mar 2025 07:39:53 GMT</pubDate>
    <dc:creator>Aleksandra_K</dc:creator>
    <dc:date>2025-03-31T07:39:53Z</dc:date>
    <item>
      <title>Weird time overhead during first call to DGEQRF and DSYRK</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/Weird-time-overhead-during-first-call-to-DGEQRF-and-DSYRK/m-p/1675848#M37001</link>
      <description>&lt;P&gt;Hello everyone,&lt;/P&gt;&lt;P&gt;I encountered odd behaviour of those procedures when called for the first time - subsequent calls take shorter execution time. I assume it is caused by some allocations made by MKL library to speed-up. What can be done to avoid such situations?&lt;/P&gt;&lt;P&gt;I attach source code of my test. I've set environmental variables OMP_NUM_THREADS and MKL_NUM_THREADS to 1.&lt;/P&gt;&lt;P&gt;Thank you for any help,&lt;BR /&gt;Jacek&lt;/P&gt;</description>
      <pubDate>Tue, 18 Mar 2025 10:26:52 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/Weird-time-overhead-during-first-call-to-DGEQRF-and-DSYRK/m-p/1675848#M37001</guid>
      <dc:creator>szachista</dc:creator>
      <dc:date>2025-03-18T10:26:52Z</dc:date>
    </item>
    <item>
      <title>Re:Weird time overhead during first call to DGEQRF and DSYRK</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/Weird-time-overhead-during-first-call-to-DGEQRF-and-DSYRK/m-p/1679170#M37019</link>
      <description>&lt;P&gt;HI Jacek,&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;When you run this function for the first time, many things happen behind the scenes, so it's normal for it to take longer. For smaller sizes, you can try using direct call or sequential mode (&lt;A href="https://www.intel.com/content/www/us/en/docs/onemkl/developer-guide-linux/2025-1/using-mkl-direct-call-in-c-applications.html" rel="noopener noreferrer" target="_blank"&gt;Using MKL_DIRECT_CALL in C Applications&lt;/A&gt;).&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Also, could you provide us with more context about what your application does and what kind of usage of oneMKL you expect? We can try to find a better solution for your case.&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Aleksandra&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;/P&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 31 Mar 2025 07:39:53 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/Weird-time-overhead-during-first-call-to-DGEQRF-and-DSYRK/m-p/1679170#M37019</guid>
      <dc:creator>Aleksandra_K</dc:creator>
      <dc:date>2025-03-31T07:39:53Z</dc:date>
    </item>
    <item>
      <title>Re: Re:Weird time overhead during first call to DGEQRF and DSYRK</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/Weird-time-overhead-during-first-call-to-DGEQRF-and-DSYRK/m-p/1679175#M37020</link>
      <description>&lt;P&gt;Hello Aleksandra,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you for your answer. Actually I was measuring time (in microseconds) of the problem involving very small matrix - later I checked for a much larger matrix and the difference was negligible, so the topic may be closed. I am sorry for confusion.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;With regards,&lt;/P&gt;&lt;P&gt;Jacek&lt;/P&gt;</description>
      <pubDate>Mon, 31 Mar 2025 07:59:02 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/Weird-time-overhead-during-first-call-to-DGEQRF-and-DSYRK/m-p/1679175#M37020</guid>
      <dc:creator>szachista</dc:creator>
      <dc:date>2025-03-31T07:59:02Z</dc:date>
    </item>
  </channel>
</rss>

