<?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 Hi, in Intel® Embree Ray Tracing Kernels</title>
    <link>https://community.intel.com/t5/Intel-Embree-Ray-Tracing-Kernels/knl/m-p/1113766#M626</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;Providing a single mrays/s number here is quite difficult as the ray tracing performance depends on so many factors, e.g. scene complexity, primitive distribution in the scene, coherent/incoherent ray distribution, whether single, packet, or ray streams are used, closest-hit or any-hit rays, SIMD utilization during shading and to generate rays, HW core/thread count, sustained core turbo frequency, work distribution among the threads etc. It might be better to benchmark the entire rendering application to get a meaningful number.&amp;nbsp; Assuming (for the sake of simplicity) that the renderer is equally efficient per clock on both a Xeon and Xeon Phi system and the work distribution scheme achieves linear scaling than the relative performance can be very roughly compared by: #cores * sustained core frequency between the two platforms.&lt;/P&gt;

&lt;P&gt;&amp;nbsp;&lt;/P&gt;

&lt;P&gt;&amp;nbsp;&lt;/P&gt;

&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 04 Jul 2016 14:25:03 GMT</pubDate>
    <dc:creator>BenthinC_Intel</dc:creator>
    <dc:date>2016-07-04T14:25:03Z</dc:date>
    <item>
      <title>knl</title>
      <link>https://community.intel.com/t5/Intel-Embree-Ray-Tracing-Kernels/knl/m-p/1113765#M625</link>
      <description>&lt;P&gt;hallo, i have seen support for knl in embree. how is the knl&lt;/P&gt;

&lt;P&gt;performance compared to std. server cpus like haswell or broadwell ?&lt;/P&gt;

&lt;P&gt;what are the embree benchmark numbers in terms of mrays/s ?&lt;/P&gt;</description>
      <pubDate>Thu, 30 Jun 2016 08:36:02 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Embree-Ray-Tracing-Kernels/knl/m-p/1113765#M625</guid>
      <dc:creator>f__n_</dc:creator>
      <dc:date>2016-06-30T08:36:02Z</dc:date>
    </item>
    <item>
      <title>Hi,</title>
      <link>https://community.intel.com/t5/Intel-Embree-Ray-Tracing-Kernels/knl/m-p/1113766#M626</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;

&lt;P&gt;Providing a single mrays/s number here is quite difficult as the ray tracing performance depends on so many factors, e.g. scene complexity, primitive distribution in the scene, coherent/incoherent ray distribution, whether single, packet, or ray streams are used, closest-hit or any-hit rays, SIMD utilization during shading and to generate rays, HW core/thread count, sustained core turbo frequency, work distribution among the threads etc. It might be better to benchmark the entire rendering application to get a meaningful number.&amp;nbsp; Assuming (for the sake of simplicity) that the renderer is equally efficient per clock on both a Xeon and Xeon Phi system and the work distribution scheme achieves linear scaling than the relative performance can be very roughly compared by: #cores * sustained core frequency between the two platforms.&lt;/P&gt;

&lt;P&gt;&amp;nbsp;&lt;/P&gt;

&lt;P&gt;&amp;nbsp;&lt;/P&gt;

&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 04 Jul 2016 14:25:03 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-Embree-Ray-Tracing-Kernels/knl/m-p/1113766#M626</guid>
      <dc:creator>BenthinC_Intel</dc:creator>
      <dc:date>2016-07-04T14:25:03Z</dc:date>
    </item>
  </channel>
</rss>

