<?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 FeatureStoreClient speed up create_training_set in Data Engineering</title>
    <link>https://community.databricks.com/t5/data-engineering/featurestoreclient-speed-up-create-training-set/m-p/54828#M30170</link>
    <description>&lt;P&gt;I am trying to create training set with 10 Feature Lookups (about 1200 features total).&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="python"&gt;# all args for create_training_set
df = fs.create_training_set(args).load_df()&lt;/LI-CODE&gt;&lt;P&gt;I must store this data to delta table for further analysis. Writing this returned data to delta table is taking up to 15 hours. How can I speed up this operation? Population size does not impact performance (same result for 200 rows)&lt;/P&gt;&lt;P&gt;Also, what is best practice for storing Feature Tables?&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://learn.microsoft.com/en-us/azure/databricks/machine-learning/feature-store/time-series" target="_blank" rel="noopener"&gt;https://learn.microsoft.com/en-us/azure/databricks/machine-learning/feature-store/time-series&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Based on documentation:&lt;BR /&gt;"&lt;SPAN&gt;A time series feature table must have one timestamp key and cannot have any partition columns. The timestamp key column must be of&amp;nbsp;&lt;/SPAN&gt;TimestampType&lt;SPAN&gt;&amp;nbsp;or&amp;nbsp;&lt;/SPAN&gt;DateType&lt;SPAN&gt;.&lt;/SPAN&gt;"&lt;/P&gt;&lt;P&gt;Is it good practice to store huge tables without partition columns?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;P.S&lt;/P&gt;&lt;P&gt;I have tried different compute types, but still getting long processing time&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 07 Dec 2023 07:09:39 GMT</pubDate>
    <dc:creator>Kira</dc:creator>
    <dc:date>2023-12-07T07:09:39Z</dc:date>
    <item>
      <title>FeatureStoreClient speed up create_training_set</title>
      <link>https://community.databricks.com/t5/data-engineering/featurestoreclient-speed-up-create-training-set/m-p/54828#M30170</link>
      <description>&lt;P&gt;I am trying to create training set with 10 Feature Lookups (about 1200 features total).&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="python"&gt;# all args for create_training_set
df = fs.create_training_set(args).load_df()&lt;/LI-CODE&gt;&lt;P&gt;I must store this data to delta table for further analysis. Writing this returned data to delta table is taking up to 15 hours. How can I speed up this operation? Population size does not impact performance (same result for 200 rows)&lt;/P&gt;&lt;P&gt;Also, what is best practice for storing Feature Tables?&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;A href="https://learn.microsoft.com/en-us/azure/databricks/machine-learning/feature-store/time-series" target="_blank" rel="noopener"&gt;https://learn.microsoft.com/en-us/azure/databricks/machine-learning/feature-store/time-series&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Based on documentation:&lt;BR /&gt;"&lt;SPAN&gt;A time series feature table must have one timestamp key and cannot have any partition columns. The timestamp key column must be of&amp;nbsp;&lt;/SPAN&gt;TimestampType&lt;SPAN&gt;&amp;nbsp;or&amp;nbsp;&lt;/SPAN&gt;DateType&lt;SPAN&gt;.&lt;/SPAN&gt;"&lt;/P&gt;&lt;P&gt;Is it good practice to store huge tables without partition columns?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;P.S&lt;/P&gt;&lt;P&gt;I have tried different compute types, but still getting long processing time&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 07 Dec 2023 07:09:39 GMT</pubDate>
      <guid>https://community.databricks.com/t5/data-engineering/featurestoreclient-speed-up-create-training-set/m-p/54828#M30170</guid>
      <dc:creator>Kira</dc:creator>
      <dc:date>2023-12-07T07:09:39Z</dc:date>
    </item>
  </channel>
</rss>

