<?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 why MKL deep learning much slow for backpropagation in Intel® oneAPI Math Kernel Library</title>
    <link>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/why-MKL-deep-learning-much-slow-for-backpropagation/m-p/1097433#M23640</link>
    <description>&lt;P&gt;according to baidu's benchmark (&lt;A href="https://github.com/baidu-research/DeepBench"&gt;https://github.com/baidu-research/DeepBench&lt;/A&gt;), mkl's deep learning with convolution (not gemm) has a much slower backward speed than the forward pass.&lt;/P&gt;

&lt;P&gt;for example (&lt;A href="https://github.com/baidu-research/DeepBench/tree/master/results"&gt;https://github.com/baidu-research/DeepBench/tree/master/results&lt;/A&gt;), for W=341, H=79,C=32,N=4, K=32, R=5, S=10, in KNL7250 platform, forward 0.91ms, backward with input is 68.79 ms, with weight is 74.98 ms! so backward is 68 times slower than forward.&lt;/P&gt;

&lt;P&gt;as a comparison, in titanx, forward is 0.74ms, backward with input is 3.09 ms, with weight is 0.76 ms. For forward, titanx is only a little faster than KNL7250, but for backward, KNL7250 is much slower. This is similar with other W,H,C configuration.&lt;/P&gt;

&lt;P&gt;can any one give me the reason? is it because mkl has not made much optimization for backward yet? it seems mkl-dnn (&lt;A href="https://github.com/01org/mkl-dnn"&gt;https://github.com/01org/mkl-dnn&lt;/A&gt;) only supports forward operations now.&lt;/P&gt;</description>
    <pubDate>Fri, 30 Sep 2016 17:57:14 GMT</pubDate>
    <dc:creator>frank_z_1</dc:creator>
    <dc:date>2016-09-30T17:57:14Z</dc:date>
    <item>
      <title>why MKL deep learning much slow for backpropagation</title>
      <link>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/why-MKL-deep-learning-much-slow-for-backpropagation/m-p/1097433#M23640</link>
      <description>&lt;P&gt;according to baidu's benchmark (&lt;A href="https://github.com/baidu-research/DeepBench"&gt;https://github.com/baidu-research/DeepBench&lt;/A&gt;), mkl's deep learning with convolution (not gemm) has a much slower backward speed than the forward pass.&lt;/P&gt;

&lt;P&gt;for example (&lt;A href="https://github.com/baidu-research/DeepBench/tree/master/results"&gt;https://github.com/baidu-research/DeepBench/tree/master/results&lt;/A&gt;), for W=341, H=79,C=32,N=4, K=32, R=5, S=10, in KNL7250 platform, forward 0.91ms, backward with input is 68.79 ms, with weight is 74.98 ms! so backward is 68 times slower than forward.&lt;/P&gt;

&lt;P&gt;as a comparison, in titanx, forward is 0.74ms, backward with input is 3.09 ms, with weight is 0.76 ms. For forward, titanx is only a little faster than KNL7250, but for backward, KNL7250 is much slower. This is similar with other W,H,C configuration.&lt;/P&gt;

&lt;P&gt;can any one give me the reason? is it because mkl has not made much optimization for backward yet? it seems mkl-dnn (&lt;A href="https://github.com/01org/mkl-dnn"&gt;https://github.com/01org/mkl-dnn&lt;/A&gt;) only supports forward operations now.&lt;/P&gt;</description>
      <pubDate>Fri, 30 Sep 2016 17:57:14 GMT</pubDate>
      <guid>https://community.intel.com/t5/Intel-oneAPI-Math-Kernel-Library/why-MKL-deep-learning-much-slow-for-backpropagation/m-p/1097433#M23640</guid>
      <dc:creator>frank_z_1</dc:creator>
      <dc:date>2016-09-30T17:57:14Z</dc:date>
    </item>
  </channel>
</rss>

