<?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: Any recommendations on instance type for z-order / vacuum/ optimize ? in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/any-recommendations-on-instance-type-for-z-order-vacuum-optimize/m-p/22341#M15294</link>
    <description>&lt;P&gt;For Delta in general having Delta cache  accelerates data reads by creating copies of remote files in nodes’ local storage using a fast intermediate data format. The data is cached automatically whenever a file has to be fetched from a remote location. Successive reads of the same data are then performed locally, which results in significantly improved reading speed. And this can be useful even when performing merges where data has to be read. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://docs.databricks.com/delta/optimizations/delta-cache.html#use-delta-caching" target="test_blank"&gt;https://docs.databricks.com/delta/optimizations/delta-cache.html#use-delta-caching&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The recommended (and easiest) way to use Delta caching is to choose a Delta Cache Accelerated—&lt;/P&gt;&lt;P&gt;i3&amp;nbsp;or&amp;nbsp;i3en&amp;nbsp;series—worker type when you configure your cluster. Such workers are enabled and configured for Delta caching.&lt;/P&gt;</description>
    <pubDate>Mon, 21 Jun 2021 20:20:44 GMT</pubDate>
    <dc:creator>aladda</dc:creator>
    <dc:date>2021-06-21T20:20:44Z</dc:date>
    <item>
      <title>Any recommendations on instance type for z-order / vacuum/ optimize ?</title>
      <link>https://community.databricks.com/t5/data-engineering/any-recommendations-on-instance-type-for-z-order-vacuum-optimize/m-p/22340#M15293</link>
      <description />
      <pubDate>Fri, 18 Jun 2021 21:15:42 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/any-recommendations-on-instance-type-for-z-order-vacuum-optimize/m-p/22340#M15293</guid>
      <dc:creator>Anonymous</dc:creator>
      <dc:date>2021-06-18T21:15:42Z</dc:date>
    </item>
    <item>
      <title>Re: Any recommendations on instance type for z-order / vacuum/ optimize ?</title>
      <link>https://community.databricks.com/t5/data-engineering/any-recommendations-on-instance-type-for-z-order-vacuum-optimize/m-p/22341#M15294</link>
      <description>&lt;P&gt;For Delta in general having Delta cache  accelerates data reads by creating copies of remote files in nodes’ local storage using a fast intermediate data format. The data is cached automatically whenever a file has to be fetched from a remote location. Successive reads of the same data are then performed locally, which results in significantly improved reading speed. And this can be useful even when performing merges where data has to be read. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://docs.databricks.com/delta/optimizations/delta-cache.html#use-delta-caching" target="test_blank"&gt;https://docs.databricks.com/delta/optimizations/delta-cache.html#use-delta-caching&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The recommended (and easiest) way to use Delta caching is to choose a Delta Cache Accelerated—&lt;/P&gt;&lt;P&gt;i3&amp;nbsp;or&amp;nbsp;i3en&amp;nbsp;series—worker type when you configure your cluster. Such workers are enabled and configured for Delta caching.&lt;/P&gt;</description>
      <pubDate>Mon, 21 Jun 2021 20:20:44 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/any-recommendations-on-instance-type-for-z-order-vacuum-optimize/m-p/22341#M15294</guid>
      <dc:creator>aladda</dc:creator>
      <dc:date>2021-06-21T20:20:44Z</dc:date>
    </item>
  </channel>
</rss>

