<?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>article How can I resolve CUDA OOM issues while performing batch inference in notebooks using ML models? in Support FAQs</title>
    <link>https://community.databricks.com/t5/support-faqs/how-can-i-resolve-cuda-oom-issues-while-performing-batch/ta-p/55583</link>
    <description>&lt;DIV class="lia-message-template-content-zone"&gt;
&lt;P&gt;&lt;SPAN&gt;The potential root cause could be high GPU utilization while running a live experiment. This can be validated both by using the Spark UI and by using the &lt;FONT face="courier new,courier"&gt;Nvidia -smi&lt;/FONT&gt; command.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;If a single GPU is explicitly used, this might cause an overload and hence OOM issues.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;To avoid OOM issues consider the following suggestions:&lt;/SPAN&gt;&lt;/P&gt;
&lt;UL&gt;
&lt;LI style="font-weight: 400;" aria-level="1"&gt;&lt;SPAN&gt;Experiment with smaller batch sizes&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI style="font-weight: 400;" aria-level="1"&gt;&lt;SPAN&gt;Use a larger GPU&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI style="font-weight: 400;" aria-level="1"&gt;&lt;SPAN&gt;Use a different framework such as Horovod&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;/DIV&gt;</description>
    <pubDate>Thu, 11 Jan 2024 01:00:00 GMT</pubDate>
    <dc:creator>Adam_Pavlacka</dc:creator>
    <dc:date>2024-01-11T01:00:00Z</dc:date>
    <item>
      <title>How can I resolve CUDA OOM issues while performing batch inference in notebooks using ML models?</title>
      <link>https://community.databricks.com/t5/support-faqs/how-can-i-resolve-cuda-oom-issues-while-performing-batch/ta-p/55583</link>
      <description>&lt;DIV class="lia-message-template-content-zone"&gt;
&lt;P&gt;&lt;SPAN&gt;The potential root cause could be high GPU utilization while running a live experiment. This can be validated both by using the Spark UI and by using the &lt;FONT face="courier new,courier"&gt;Nvidia -smi&lt;/FONT&gt; command.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;If a single GPU is explicitly used, this might cause an overload and hence OOM issues.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;To avoid OOM issues consider the following suggestions:&lt;/SPAN&gt;&lt;/P&gt;
&lt;UL&gt;
&lt;LI style="font-weight: 400;" aria-level="1"&gt;&lt;SPAN&gt;Experiment with smaller batch sizes&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI style="font-weight: 400;" aria-level="1"&gt;&lt;SPAN&gt;Use a larger GPU&lt;/SPAN&gt;&lt;/LI&gt;
&lt;LI style="font-weight: 400;" aria-level="1"&gt;&lt;SPAN&gt;Use a different framework such as Horovod&lt;/SPAN&gt;&lt;/LI&gt;
&lt;/UL&gt;
&lt;/DIV&gt;</description>
      <pubDate>Thu, 11 Jan 2024 01:00:00 GMT</pubDate>
      <guid>https://community.databricks.com/t5/support-faqs/how-can-i-resolve-cuda-oom-issues-while-performing-batch/ta-p/55583</guid>
      <dc:creator>Adam_Pavlacka</dc:creator>
      <dc:date>2024-01-11T01:00:00Z</dc:date>
    </item>
  </channel>
</rss>

