<?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: How does running VACUUM on Delta Lake tables effect read/write performance? in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/how-does-running-vacuum-on-delta-lake-tables-effect-read-write/m-p/25249#M17541</link>
    <description>&lt;P&gt;VACUUM has no effect on read/write performance to that table. Never running VACUUM on a table will not make read/write performance to a Delta Lake table any slower.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you run VACUUM very infrequently, your VACUUM runtimes themselves may be pretty high, so it is suggested to run VACUUM somewhat regularly. How often you should run VACUUM depends on your storage costs.&lt;/P&gt;</description>
    <pubDate>Wed, 23 Jun 2021 21:24:26 GMT</pubDate>
    <dc:creator>User16783853906</dc:creator>
    <dc:date>2021-06-23T21:24:26Z</dc:date>
    <item>
      <title>How does running VACUUM on Delta Lake tables effect read/write performance?</title>
      <link>https://community.databricks.com/t5/data-engineering/how-does-running-vacuum-on-delta-lake-tables-effect-read-write/m-p/25247#M17539</link>
      <description>&lt;P&gt;If I don't run VACUUM on a Delta Lake table, will that make my read performance slower?&lt;/P&gt;</description>
      <pubDate>Thu, 10 Jun 2021 21:47:11 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/how-does-running-vacuum-on-delta-lake-tables-effect-read-write/m-p/25247#M17539</guid>
      <dc:creator>User16783853906</dc:creator>
      <dc:date>2021-06-10T21:47:11Z</dc:date>
    </item>
    <item>
      <title>Re: How does running VACUUM on Delta Lake tables effect read/write performance?</title>
      <link>https://community.databricks.com/t5/data-engineering/how-does-running-vacuum-on-delta-lake-tables-effect-read-write/m-p/25248#M17540</link>
      <description>&lt;P&gt;VACUUM does not have a direct impact on read/write performance since it only remove files no longer referenced by a Delta table ( unless your data volume is so high that you are hitting the read limits of underlying S3/GCS/ADLS buckets ) .  It would make sense to run it as a separate job scheduled daily and potentially using sport instances &lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 17 Jun 2021 22:39:29 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/how-does-running-vacuum-on-delta-lake-tables-effect-read-write/m-p/25248#M17540</guid>
      <dc:creator>sajith_appukutt</dc:creator>
      <dc:date>2021-06-17T22:39:29Z</dc:date>
    </item>
    <item>
      <title>Re: How does running VACUUM on Delta Lake tables effect read/write performance?</title>
      <link>https://community.databricks.com/t5/data-engineering/how-does-running-vacuum-on-delta-lake-tables-effect-read-write/m-p/25249#M17541</link>
      <description>&lt;P&gt;VACUUM has no effect on read/write performance to that table. Never running VACUUM on a table will not make read/write performance to a Delta Lake table any slower.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you run VACUUM very infrequently, your VACUUM runtimes themselves may be pretty high, so it is suggested to run VACUUM somewhat regularly. How often you should run VACUUM depends on your storage costs.&lt;/P&gt;</description>
      <pubDate>Wed, 23 Jun 2021 21:24:26 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/how-does-running-vacuum-on-delta-lake-tables-effect-read-write/m-p/25249#M17541</guid>
      <dc:creator>User16783853906</dc:creator>
      <dc:date>2021-06-23T21:24:26Z</dc:date>
    </item>
  </channel>
</rss>

