<?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: Job optimization in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/job-optimization/m-p/94833#M38977</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;You can check below components for Managing Idle Costs:&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Auto-scaling and Auto-termination:&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;Auto-scaling: Enable auto-scaling to dynamically adjust the number of worker nodes based on job requirements. This helps in scaling up during high demand and scaling down during low demand.&lt;BR /&gt;Auto-termination: Configure clusters to automatically terminate after a set period of inactivity. This prevents idle clusters from incurring unnecessary costs.&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Use Job Compute:&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;Job Compute vs. All-Purpose Compute: Running non-interactive workloads on job compute instances is more cost-effective than using all-purpose compute instances.&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Choose the Right Instance Type&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;Instance Type Selection: Select instance types based on workload characteristics. For example, use memory-optimized instances for ML tasks and compute-optimized instances for streaming workloads.&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Efficient Compute Size:&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;Compute Sizing Considerations: Consider factors like total executor cores, memory, and local storage when sizing your compute. This ensures optimal resource utilization and cost efficiency.&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Design Cost-effective Workloads:&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;Balance Always-on and Triggered Streaming: For use cases that do not require immediate data updates, schedule fewer runs to reduce costs.&lt;/P&gt;
&lt;P&gt;Check the doc: &lt;A href="https://docs.databricks.com/en/lakehouse-architecture/cost-optimization/best-practices.html" target="_blank"&gt;https://docs.databricks.com/en/lakehouse-architecture/cost-optimization/best-practices.html&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Fri, 18 Oct 2024 11:07:59 GMT</pubDate>
    <dc:creator>shashank853</dc:creator>
    <dc:date>2024-10-18T11:07:59Z</dc:date>
    <item>
      <title>Job optimization</title>
      <link>https://community.databricks.com/t5/data-engineering/job-optimization/m-p/94832#M38976</link>
      <description>&lt;P&gt;How to increase the resource efficiency in databricks jobs?&lt;/P&gt;&lt;P&gt;We see that idle cost is more than the utilization cost. Any guidelines will be helpful&lt;/P&gt;&lt;P&gt;&amp;nbsp;Please share some examples.&lt;/P&gt;</description>
      <pubDate>Fri, 18 Oct 2024 11:02:35 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/job-optimization/m-p/94832#M38976</guid>
      <dc:creator>sashikanth</dc:creator>
      <dc:date>2024-10-18T11:02:35Z</dc:date>
    </item>
    <item>
      <title>Re: Job optimization</title>
      <link>https://community.databricks.com/t5/data-engineering/job-optimization/m-p/94833#M38977</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;You can check below components for Managing Idle Costs:&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Auto-scaling and Auto-termination:&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;Auto-scaling: Enable auto-scaling to dynamically adjust the number of worker nodes based on job requirements. This helps in scaling up during high demand and scaling down during low demand.&lt;BR /&gt;Auto-termination: Configure clusters to automatically terminate after a set period of inactivity. This prevents idle clusters from incurring unnecessary costs.&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Use Job Compute:&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;Job Compute vs. All-Purpose Compute: Running non-interactive workloads on job compute instances is more cost-effective than using all-purpose compute instances.&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Choose the Right Instance Type&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;Instance Type Selection: Select instance types based on workload characteristics. For example, use memory-optimized instances for ML tasks and compute-optimized instances for streaming workloads.&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Efficient Compute Size:&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;Compute Sizing Considerations: Consider factors like total executor cores, memory, and local storage when sizing your compute. This ensures optimal resource utilization and cost efficiency.&lt;/P&gt;
&lt;P&gt;&lt;STRONG&gt;Design Cost-effective Workloads:&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;Balance Always-on and Triggered Streaming: For use cases that do not require immediate data updates, schedule fewer runs to reduce costs.&lt;/P&gt;
&lt;P&gt;Check the doc: &lt;A href="https://docs.databricks.com/en/lakehouse-architecture/cost-optimization/best-practices.html" target="_blank"&gt;https://docs.databricks.com/en/lakehouse-architecture/cost-optimization/best-practices.html&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 18 Oct 2024 11:07:59 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/job-optimization/m-p/94833#M38977</guid>
      <dc:creator>shashank853</dc:creator>
      <dc:date>2024-10-18T11:07:59Z</dc:date>
    </item>
    <item>
      <title>Re: Job optimization</title>
      <link>https://community.databricks.com/t5/data-engineering/job-optimization/m-p/94841#M38979</link>
      <description>&lt;P&gt;My main improvements are:&lt;/P&gt;&lt;P&gt;- use singlenode job clusters for small data&lt;BR /&gt;- cluster reuse (so use the same job cluster for multiple tasks, in parallel or serial)&lt;BR /&gt;- use autoscaling only when it is very hard to find a good fixed sizing, otherwise go for fixed size.&lt;/P&gt;</description>
      <pubDate>Fri, 18 Oct 2024 11:50:52 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/job-optimization/m-p/94841#M38979</guid>
      <dc:creator>-werners-</dc:creator>
      <dc:date>2024-10-18T11:50:52Z</dc:date>
    </item>
  </channel>
</rss>

