MYSQL Time
Hi,
Is there a way to cut down the time of MYSQL dataflows?
I have a dataflow that takes 6 hours for 5 million rows of data and would love to find a way to cut that down.
Best Answer
-
You can try and implement indexes in your MySQL dataflow however I'd HIGHLY recommend rewriting your MySQL dataflow in Magic ETL as MySQL is sequential (it has to wait for each dataset load or step to complete before it can move to the next one) compared to Magic's sequential processing (can do many steps simultaneously).
I've seen improvements of over 90% when converting MySQL to Magic ETL.
**Was this post helpful? Click Agree or Like below**
**Did this solve your problem? Accept it as a solution!**1
Answers
-
You can try and implement indexes in your MySQL dataflow however I'd HIGHLY recommend rewriting your MySQL dataflow in Magic ETL as MySQL is sequential (it has to wait for each dataset load or step to complete before it can move to the next one) compared to Magic's sequential processing (can do many steps simultaneously).
I've seen improvements of over 90% when converting MySQL to Magic ETL.
**Was this post helpful? Click Agree or Like below**
**Did this solve your problem? Accept it as a solution!**1 -
I will give that a try, thank you.
0
Categories
- All Categories
- 1.7K Product Ideas
- 1.7K Ideas Exchange
- 1.5K Connect
- 1.2K Connectors
- 292 Workbench
- 4 Cloud Amplifier
- 8 Federated
- 2.8K Transform
- 95 SQL DataFlows
- 601 Datasets
- 2.1K Magic ETL
- 3.7K Visualize
- 2.4K Charting
- 689 Beast Mode
- 43 App Studio
- 39 Variables
- 658 Automate
- 170 Apps
- 441 APIs & Domo Developer
- 42 Workflows
- 5 DomoAI
- 32 Predict
- 12 Jupyter Workspaces
- 20 R & Python Tiles
- 385 Distribute
- 110 Domo Everywhere
- 269 Scheduled Reports
- 6 Software Integrations
- 112 Manage
- 109 Governance & Security
- 8 Domo University
- 25 Product Releases
- Community Forums
- 39 Getting Started
- 29 Community Member Introductions
- 98 Community Announcements
- Domo Community Gallery
- 4.8K Archive