Magic ETL - Using Group by - run time impact question
Wondering what is the best practice to reduce overall run time of a ETL dataflow...
I've got 5 input datasets totalling about 14M rows of data that are ultimately appended together in the final result.
Is it better to use group by in the magic ETL for each dataset (5 steps) or one consolidated step after the appends?
Also, are there certain items in Magic ETL that are run time bandits?
- 10.7K All Categories
- 13 Getting Started in the Community
- 41 Beastmode & Analytics
- 2.1K Data Platform & Data Science
- 59 Domo Everywhere
- 2.7K Charting
- 2.5K Ideas Exchange
- 1.3K Connectors
- 362 Workbench
- 303 Use Cases & Best Practices
- 503 APIs
- 120 Apps
- 48 News
- 753 Onboarding
- 1.2K 日本支部
- Private Company Board