Optimum set up for Dataflows

Hi， CrazyHorse66 

a. The main purpose of using the Enhanced Compute Engine is to drastically reduce the refresh time required for long-running ETL steps on compute entities. If you have many ETL operations (such as performing joins, distinct, filte) on S2, you should enable the enhanced compute engine for S2.

b.The following list describes some of the reasons you may choose to use linked tables:

• If you want to reuse a table across multiple dataflows, such as a date table or a static lookup table, you should create a table once and then reference it across the other dataflows.

• If you want to avoid creating multiple refreshes to a data source, it's better to use linked tables to store the data and act as a cache. Doing so allows every subsequent consumer to leverage that table, reducing the load to the underlying data source.

• If you need to perform a merge between two tables.

c.You can use DirectQuery to connect directly to your dataflow, and thereby connect directly to your dataflow without having to import its data. Direct query avoids separate refresh schedules and it is aslo useful for working on a filtered view of data inside a dataflow. 
Limitation: Large dataflows may have trouble with timeout issues when viewing visualizations. Large dataflows that run into trouble with timeout issues should use Import mode.

d. Personally, I also prefer to use Power Automate to trigger multiple dataflows and Power BI datasets sequentially.

Please refer to below tutorials for more details.
Premium features of dataflows 

Create a dataflow using linked tables 

Best Regards,
Community Support Team _ Eason