<?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 What is the performance impact of changing dataSkippingNumIndexedCols from 32 to 16? in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/what-is-the-performance-impact-of-changing/m-p/4158#M958</link>
    <description>&lt;P&gt;I already improved a lot the performances of our ETL (x20 !) but I still want to know where I can improve performances. I seems that tables stats and column indexing slow down a bit writings so I want to decrease &lt;B&gt;dataSkippingNumIndexedCols&amp;nbsp;&lt;/B&gt;to match the small columns subset on which filters are actually applied, and columns with low distinct values. I wonder if it's worth doing that because it requires development work and columns order is imposed.&lt;/P&gt;&lt;P&gt;The documentation says it is worth doing that if your columns contain textual information for example because indexing is inefficient.&lt;/P&gt;</description>
    <pubDate>Fri, 19 May 2023 10:07:11 GMT</pubDate>
    <dc:creator>Thor</dc:creator>
    <dc:date>2023-05-19T10:07:11Z</dc:date>
    <item>
      <title>What is the performance impact of changing dataSkippingNumIndexedCols from 32 to 16?</title>
      <link>https://community.databricks.com/t5/data-engineering/what-is-the-performance-impact-of-changing/m-p/4158#M958</link>
      <description>&lt;P&gt;I already improved a lot the performances of our ETL (x20 !) but I still want to know where I can improve performances. I seems that tables stats and column indexing slow down a bit writings so I want to decrease &lt;B&gt;dataSkippingNumIndexedCols&amp;nbsp;&lt;/B&gt;to match the small columns subset on which filters are actually applied, and columns with low distinct values. I wonder if it's worth doing that because it requires development work and columns order is imposed.&lt;/P&gt;&lt;P&gt;The documentation says it is worth doing that if your columns contain textual information for example because indexing is inefficient.&lt;/P&gt;</description>
      <pubDate>Fri, 19 May 2023 10:07:11 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/what-is-the-performance-impact-of-changing/m-p/4158#M958</guid>
      <dc:creator>Thor</dc:creator>
      <dc:date>2023-05-19T10:07:11Z</dc:date>
    </item>
  </channel>
</rss>

