Apache Spark Core-Deep Dive-Proper Optimization Daniel Tomes Databricks

  Рет қаралды 185,404

Databricks

Databricks

Күн бұрын

Пікірлер: 83
@xinyuan6649
@xinyuan6649 2 жыл бұрын
This is so far the most informative and in-depth talk about spark job optimization I found on KZbin. Before this, the opt I've been doing is mostly through blindly trial & error. Thank you so much Daniel, it's amazing to see someone who can break a (sometimes) overwhelming task into basic spark concepts and apply deductive & inductive analysis.
@danieltomes8566
@danieltomes8566 5 жыл бұрын
Hello folks, thanks for all the support. Sorry for the delay on the Ebook, it's still coming it was just delayed. I will share it here as soon as it's available. I'm hoping Q1 this year. :)
@GenerativeAI-Guru
@GenerativeAI-Guru 4 жыл бұрын
Thanks!
@ajaypratap4025
@ajaypratap4025 4 жыл бұрын
Thanks Daniel, great talk. Please share the ebook, once completed.
@moha081
@moha081 4 жыл бұрын
Hello Daniel, when i checked spark documnetation, i found that the cache is equal to persistent with MEMORY_ONLY option, did the rdd.cache is different than df.cache??? spark.apache.org/docs/latest/rdd-programming-guide.html#rdd-persistence Thanks
@luxsasha
@luxsasha 4 жыл бұрын
any update @daniel ?
@SpiritOfIndiaaa
@SpiritOfIndiaaa 4 жыл бұрын
Nice 👍, any updates on eBook?
@aleixfalguerascasals3329
@aleixfalguerascasals3329 Жыл бұрын
The best talk about spark optimizations in YT by far, thanks man!
@leoezhil5304
@leoezhil5304 Жыл бұрын
Really very good session Dan. It’s my pleasure to work with you.
@НикитаБ-ф1ю
@НикитаБ-ф1ю 3 жыл бұрын
50:49 what is the purpose of adding a constant to each row? They key will not change, it will still be computed on 1 executor. The salt column value should be different for different rows to split large key.
@thomsondcruz5456
@thomsondcruz5456 3 жыл бұрын
4:45 1 Task = 1 Core can be changed using the property spark.task.cpu. The default is 1 Task = 1 Core.
@nupoornawathey100
@nupoornawathey100 5 ай бұрын
Redirected to this page from SO, class apart content. Glad to find this goldmine !!
@AshikaUmanga
@AshikaUmanga 5 жыл бұрын
In the lazy-loading, he filtered the years from 2000-2001 , what if the calculation should be done for all the years? Can't use a filter in this case right ?
@joshuahendinata3594
@joshuahendinata3594 4 жыл бұрын
I believe he is just using filter to reduce the number of rows to join. I think you must have the knowledge regarding the input data and know that outside a particular range, the data will have a match in the join
@JaX0rton
@JaX0rton 4 жыл бұрын
+1. I think the idea is to filter as far upstream as possible. Don't do a cartesian product and then a filter if you can filter is ahead of time.
@michailanastasopoulos1084
@michailanastasopoulos1084 5 жыл бұрын
Why are 540 partitions not good? It is explained at 24:42 but I didn't quite get it.
@michailanastasopoulos1084
@michailanastasopoulos1084 5 жыл бұрын
OK, got it now: Each core processes one 100 MB partition. We have 96 cores that need to process a total of 54 GB. At a given time or batch all 96 cores can process a maximum of 96x100=9600MB. That means after 5 batches the cluster processes 9600MBx5=48000MB. For the last batch the cluster needs to process the remaining 6000MB or 6000MB/100=60 partitions. Those 60 partitions will be processed by 60 processors which is 62,5% of the cluster. The remaining 36 processors which is 37,5% of the cluster will be idle in the last batch. The story looks different if we had 480 112,5 MB partitions. This gives us 10800 MB per batch. And all data are processed after 5 batches with 100% CPU utilization.
@joshuahendinata3594
@joshuahendinata3594 4 жыл бұрын
@@michailanastasopoulos1084 Thank you so much. A much needed explanation!
@ejmsp
@ejmsp 4 жыл бұрын
@@michailanastasopoulos1084 thanks, i was with the same doubt
@bikashpatra119
@bikashpatra119 4 жыл бұрын
@@michailanastasopoulos1084 can you please help me understand why the partition size is decided to be 100MB?
@amontesi
@amontesi 2 жыл бұрын
@@bikashpatra119 my guess is that just because it is less than the notional upper bound of 150-200 MB/partition. There doesn't seem to be a formula that will return the amount of spill, given a number of inputs (i.e. shuffle input size and list of tasks on this stage) but since the general logic is "smaller target partition sizes result in a reduction of spill, even if we cannot predict how much spill will result, let's just fastrack the spill reduction process by just halving the notional upper bound for the target partition size of 200 MB/partition".
@syedshahasad9551
@syedshahasad9551 4 жыл бұрын
Excellent explanations. Cleared so many wrong concepts of mine. Thanks man!!!!
@SpiritOfIndiaaa
@SpiritOfIndiaaa 4 жыл бұрын
if you are adding "salt" column in groupBy it would give wrong results right ... if any groupBy function results we required ?
@rushabhgujarathi1254
@rushabhgujarathi1254 4 жыл бұрын
Yes, you are right I had the same question initially.This can be solved by running additional group by on the obtained dataset as this will run fast.We are using 2 group by to avoid skew.
@manjy5927
@manjy5927 6 ай бұрын
Thanks, your video helps me keep my job
@saravanannagarajan1169
@saravanannagarajan1169 3 жыл бұрын
good job Daniel Tomes. It help lots
@Taczan1
@Taczan1 3 жыл бұрын
Great talk! Many Thanks. Btw, where is the book, Daniel? :)
@SandeepPatel-wt7ye
@SandeepPatel-wt7ye 3 жыл бұрын
Thanks, Daniel, great talk. Please share the ebook link.
@manishmittal595
@manishmittal595 4 жыл бұрын
Hi...Great Presentation for understanding Spark optimizations. Is there any Presentation slides to go through..since in videos..its little difficult to read those numbers...
@entertainmentvlogs9634
@entertainmentvlogs9634 3 жыл бұрын
How to set the spark.sql.shuffle.partition by a variable instead of a constant..means if the shuffle input data size is less then it should automatically choose less number of SQL shuffle partition if input shuffle data stage is more then the job should programmaticaly be able to determine correct partition..rather then given a constant valuem
@129ravi
@129ravi 5 жыл бұрын
is the ebook available?
@SpiritOfIndiaaa
@SpiritOfIndiaaa 4 жыл бұрын
@1:00:28 min line 22 i.e. save(histPerfPath_1y) does it work if I run it on cluster to save on hdfs path ? in foreach if i save and run it in yarn-cluster mode it would fail to save with error... hdfs temp file wont find to save.... how to solve this kind of issue ?
@sureshsindhwani6317
@sureshsindhwani6317 4 жыл бұрын
Super talk Daniel and great insights, still waiting for the ebook though :)
@kyleligon2472
@kyleligon2472 5 жыл бұрын
Great talk! Really learned alot, looking forward to the book!
@TheRags080484
@TheRags080484 5 жыл бұрын
What is the name of the book? When will it come out?
@khaledarja9239
@khaledarja9239 4 жыл бұрын
Lazy loading it is just a matter of adding a filter?
@JaX0rton
@JaX0rton 4 жыл бұрын
Can we get a link to the slides? There are tons of small details on the slides that will be easier to go through if we have the slides rather than pausing the video every time. :)
@LaxmanKumarMunigala
@LaxmanKumarMunigala 4 жыл бұрын
Is there a github or some other place the data used for this exercise and the code?
@nebimertaydin3187
@nebimertaydin3187 Жыл бұрын
what's the link for range join optimization reference?
@chenlin6683
@chenlin6683 5 жыл бұрын
Could you share the slides of this topic?
@DCameronMauch
@DCameronMauch 5 жыл бұрын
He mentioned that the slide deck would be available. Does anyone know where to find it?
@lbam28
@lbam28 4 жыл бұрын
Great talk, with a lot takeaways!! Is there any references to the notebooks with datasets so I can recreate some of the optimizations?
@dagmawimengistu4474
@dagmawimengistu4474 4 жыл бұрын
How did you come up with the 16mb maxPartitionBytes? is there a general formula for it?
@michalsankot
@michalsankot 4 жыл бұрын
Excellent talk Daniel 👍 I wish I saw it when I started with Spark :-) How's it looking with mentioned e-book?
@SpiritOfIndiaaa
@SpiritOfIndiaaa 4 жыл бұрын
thank you so much for explaining slat addition clearly.
@SuperFatafati
@SuperFatafati 3 жыл бұрын
what command do we use to use all 96 cores while writing instead of only 10?
@SpiritOfIndiaaa
@SpiritOfIndiaaa 4 жыл бұрын
@45 min , why broadcast has 4 times 12 =48 ? it should be 3 times 12 = 36 right? as we have 3 executors ?
@rushabhgujarathi1254
@rushabhgujarathi1254 4 жыл бұрын
The memory will reduce to 36 GB once the GC kicks in,as the data is still lying in the memory of all the executors that is it is 48 GB.
@aymiraydinli5655
@aymiraydinli5655 9 ай бұрын
I am curious, if setting partition sizes that small, would cause a small file issue or maybe I am missing something. Can please someone answer?
@fernandoplak6925
@fernandoplak6925 Ай бұрын
Yeah that's a good point. There will always be a tradeoff, probably most of the times it's worth to have the executors running smoothly and handling the small files later.
@programminginterviewsprepa7710
@programminginterviewsprepa7710 2 жыл бұрын
If a system is created that you have to tweak it so much and understand it so much to get good performance I would say it should be redesigned
@saiyijinprince
@saiyijinprince 4 жыл бұрын
Why is the first example a valid comparison? You reduced the size of the data you are working with so obviously it will run faster. What if you actually need to process all years instead of just two?
@mdtausif3480
@mdtausif3480 3 жыл бұрын
I have the same question.. didn't get how reducing the number of input file is an optimization.
@Oscar-pj5cb
@Oscar-pj5cb 2 жыл бұрын
Could you share slide?
@SpiritOfIndiaaa
@SpiritOfIndiaaa 4 жыл бұрын
what do mean by saying ... have array of table names and parallelize it ... wht you mean parallelize here ?
@khuatdinh
@khuatdinh Жыл бұрын
He meant kinda ideas of “multiple threads” for spark jobs for list of tables
@veerasekharadasandam139
@veerasekharadasandam139 3 жыл бұрын
good insights, really helpful.
@Elkhamasi
@Elkhamasi 4 ай бұрын
I will obviously come back for reference
@vchandm23
@vchandm23 2 жыл бұрын
This video is Gold stuff
@AB-xg1qb
@AB-xg1qb 5 жыл бұрын
it is very helpful ! Can some one share the Ebook
@SpiritOfIndiaaa
@SpiritOfIndiaaa 4 жыл бұрын
@22 min where did you get Stage 21 shuffle input size ?
@Prashanth-yj6qx
@Prashanth-yj6qx 7 ай бұрын
Can anyone tell me why he reduced target size to 100 mB from 200mb
@sermoacidus
@sermoacidus 4 ай бұрын
to equally utilize all the cores
@ajithkannan522
@ajithkannan522 Жыл бұрын
Awesome awesome awesome
@raksadi8465
@raksadi8465 4 жыл бұрын
In my spark version 2.4.3 job after all my transformations,computations and joins I am writing my final dataframe to s3 in parquet format But irrespective of my cores count my job is taking fixed amount for completing save action For distinct cores count-8,16,24 my write action timing is fixed to 8 minutes Due to this my solution is not becoming scalable How should I make my solution scalable so that my overall job execution time becomes proportional to cores used
@vinayakmishra1837
@vinayakmishra1837 3 жыл бұрын
God Level
@hseham100
@hseham100 5 жыл бұрын
great one
@gardnmi
@gardnmi Жыл бұрын
It's almost 2024 and the default 200 shuffle partitions are still wreaking havoc on pipelines.
@vliopard
@vliopard 10 ай бұрын
I was trying to load 600 million rows to a pandas dataframe from SQL Server. It was taking too long and then OOM error. I tought pyspark will solve that problem. But after 42 minutes watching this video, I see that's better using a cluster with more RAM and raise SQL Server processor. Most of requirements to setup pyspark are not known on my environment so pyspark is useless when you are working with data you don't know details about.
@raviiit6415
@raviiit6415 Жыл бұрын
watched it
@Gerald-iz7mv
@Gerald-iz7mv Жыл бұрын
are all pandas UDF vectorized?
@AnkushSingh-hi6gj
@AnkushSingh-hi6gj 4 жыл бұрын
I can never do all of it
@harshthakur3248
@harshthakur3248 Жыл бұрын
Checking if you can 😅
@TheRags080484
@TheRags080484 5 жыл бұрын
Is the e-book available?
Making Apache Spark™ Better with Delta Lake
58:10
Databricks
Рет қаралды 180 М.
1% vs 100% #beatbox #tiktok
01:10
BeatboxJCOP
Рет қаралды 67 МЛН
How Strong Is Tape?
00:24
Stokes Twins
Рет қаралды 96 МЛН
Try this prank with your friends 😂 @karina-kola
00:18
Andrey Grechka
Рет қаралды 9 МЛН
Quando A Diferença De Altura É Muito Grande 😲😂
00:12
Mari Maria
Рет қаралды 45 МЛН
Delta Live Tables A to Z: Best Practices for Modern Data Pipelines
1:27:52
Advancing Spark - Understanding the Spark UI
30:19
Advancing Analytics
Рет қаралды 55 М.
A Deep Dive into Spark SQL's Catalyst Optimizer with Yin Huai
28:09
Unity Catalog Community Meetup - December 5, 2024
26:48
Unity Catalog
Рет қаралды 194
1% vs 100% #beatbox #tiktok
01:10
BeatboxJCOP
Рет қаралды 67 МЛН