Why OneLake is a BIG DEAL in Microsoft Fabric (with Pawel Potasinski)

  Рет қаралды 1,933

Havens Consulting

Havens Consulting

Күн бұрын

Пікірлер: 3
@noahhadro8213
@noahhadro8213 Жыл бұрын
Unfortunately Direct Lake mode is not near as fast as Import mode. We ran a test where we used Data Flows GEN 2 to bring in a fact table with 30M records and one dimension into the fabric lake house from SQL on prem. We created a dataset from that using direct lake mode. Then we created another dataset with the same fact table and dimension using import mode. We did a simple SUMX calculation in both datasets. We ran the query several times clearing the cache for both before we ran each time. The Import mode ran twice as fast. 408 ms imported vs 934 ms direct lake mode. Is this what you are experiencing?
@HavensConsulting
@HavensConsulting Жыл бұрын
Message from Pawel 🙂 Thanks for this comment and sharing the result of your test! My general comment is that our "north star" for Direct Lake is that it would be as fast as Import mode, but for now it's not always like that, especially "out-of-the-box". Two thoughts related to your test: 1) Dataflows Gen2 used to be known of generating nonoptimal Delta tables (see this blog post by Sandeep Pawar: fabric.guru/fabric-not-all-delta-tables-are-created-equally). It's still in Public Preview! :-) 2) Have you made sure your Delta tables are optimized by using V-Order (see learn.microsoft.com/en-us/fabric/data-engineering/delta-optimization-and-v-order?tabs=sparksql)? There is a super easy way to optimize specific Delta table directly from Fabric UI - simply right-click on your table and select the Optimize option. In addition, here's another great blog post from Sandeep on how to check if Delta table is V-Order optimized: fabric.guru/checking-if-delta-table-in-fabric-is-v-order-optimized.
@muppetbaer
@muppetbaer Жыл бұрын
Direct Lake is marginally slower vs import (for now), but, for me, the use case for Direct Lake is in allowing dataset complexity that import cannot even approach. Yeah, it's 0.5 seconds slower over 32M table with a single dim. How about trying to run a model with 10x 250M fact tables, 50ish partitions, multiple pipelines upserting data non-stop throughout the day, a dozen of derivative models serving 100ish users each, and syncing to warehouse mirrors using shortcuts. Try doing that in import.
Supercharge your Power BI Monitoring with Argus PBI (with Greg Baldini)
1:07:53
DAX Query View Testing Patterns (with John Kerski)
1:02:52
Havens Consulting
Рет қаралды 1,2 М.
Гениальное изобретение из обычного стаканчика!
00:31
Лютая физика | Олимпиадная физика
Рет қаралды 4,8 МЛН
Try this prank with your friends 😂 @karina-kola
00:18
Andrey Grechka
Рет қаралды 9 МЛН
REAL or FAKE? #beatbox #tiktok
01:03
BeatboxJCOP
Рет қаралды 18 МЛН
Semantic Model Ideation for Power BI (Leslie Welch)
1:11:40
Havens Consulting
Рет қаралды 2 М.
Transform productivity with AI experiences in Microsoft Fabric | OD24
26:11
Microsoft Developer
Рет қаралды 6 М.
Star Schema in Fabric? - Ep.259 - Power BI tips from the Real World
1:07:11
Empower every BI professional to do more with Microsoft Fabric | OD06
29:58
Microsoft Developer
Рет қаралды 21 М.
Copilot in Microsoft Fabric | Ultimate demo of copilots in Notebooks - DS & DE
15:42
Azure Synapse Analytics
Рет қаралды 2,6 М.
Creating A Microsoft Fabric End-To-End Solution ⚡ [Full Course]
1:30:01
Microsoft Fabric Lakehouse
16:39
RADACAD
Рет қаралды 17 М.
Visual Calculations in Power BI - DAX Made Easy! [Full Course]
1:30:40
Pragmatic Works
Рет қаралды 96 М.
Гениальное изобретение из обычного стаканчика!
00:31
Лютая физика | Олимпиадная физика
Рет қаралды 4,8 МЛН