<?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: BLOCK_SIZE in vdRngLognormal in Intel® oneAPI Math Kernel Library</title>
    <link>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/BLOCK-SIZE-in-vdRngLognormal/m-p/992305#M18056</link>
    <description>The only reason to block is to use cache more effectively. You want a blocksize large enough that the VSL performance approaches the asymptotic performance for the function (see &lt;A href="http://www.intel.com/software/products/mkl/data/vsl/vsl_performance_data.htm)" target="_blank"&gt;http://www.intel.com/software/products/mkl/data/vsl/vsl_performance_data.htm)&lt;/A&gt; but is not so large that there is cache thrashing.

As the performance reference shows, vectors of about 1K in length give you a substantial percentage of the ultimate performance for the various random number generators.

Bruce</description>
    <pubDate>Mon, 18 Apr 2005 05:26:23 GMT</pubDate>
    <dc:creator>Intel_C_Intel</dc:creator>
    <dc:date>2005-04-18T05:26:23Z</dc:date>
    <item>
      <title>BLOCK_SIZE in vdRngLognormal</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/BLOCK-SIZE-in-vdRngLognormal/m-p/992304#M18055</link>
      <description>&lt;DIV&gt;&lt;/DIV&gt;
&lt;DIV&gt;I am new to using IMKL. I will be primarily using in for running numerical simulations. In trying to understand how to use MKL I was programming in an example from Sergey Maidanov's paper Monte Carlo Options Pricing Using Various Industry Library Solutions, which I got from the Intel web site. In this paper for MKL he uses a variable called BLOCK_SIZE when he sets up his call to vdRngLognormal. He doesn't doesn't give a value for BLOCK_SIZE nor does he give any explanation on how to determine what it should be. Is the value for BLOCK_SIZE that will give the best performance dependent on the machine the code is run on, or the BRNG that is called for the random numbers?&lt;/DIV&gt;</description>
      <pubDate>Fri, 15 Apr 2005 23:56:05 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/BLOCK-SIZE-in-vdRngLognormal/m-p/992304#M18055</guid>
      <dc:creator>ron_sobey</dc:creator>
      <dc:date>2005-04-15T23:56:05Z</dc:date>
    </item>
    <item>
      <title>Re: BLOCK_SIZE in vdRngLognormal</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/BLOCK-SIZE-in-vdRngLognormal/m-p/992305#M18056</link>
      <description>The only reason to block is to use cache more effectively. You want a blocksize large enough that the VSL performance approaches the asymptotic performance for the function (see &lt;A href="http://www.intel.com/software/products/mkl/data/vsl/vsl_performance_data.htm)" target="_blank"&gt;http://www.intel.com/software/products/mkl/data/vsl/vsl_performance_data.htm)&lt;/A&gt; but is not so large that there is cache thrashing.

As the performance reference shows, vectors of about 1K in length give you a substantial percentage of the ultimate performance for the various random number generators.

Bruce</description>
      <pubDate>Mon, 18 Apr 2005 05:26:23 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/BLOCK-SIZE-in-vdRngLognormal/m-p/992305#M18056</guid>
      <dc:creator>Intel_C_Intel</dc:creator>
      <dc:date>2005-04-18T05:26:23Z</dc:date>
    </item>
  </channel>
</rss>

