Java ExecutorService - Part 1 - Introduction 

Really explained well. This is the best I have found till now. Thank you. Keep up the good work :)

Thank you, you have a skill for explaining complex concepts in a clear concise manner. I would love to see full fledged courses created by you.

Loved the explanation. Just a lame question. For a CPU intense operation, shouldn't the ideal thread pool size be (no of cores-1) as there is already a main thread running?

A very intelligent statement. If your tasks are I/O intensive e.g. DB calls, Network calls. Most of the threads would be in waiting state (waiting for DB response or Network call response) in such a scenario having a large thread pool is the right way to go. That way you would be able to start more tasks. Thanks

Done thanks Thread pool instead of creating a 1000 threads which is expensive, can make a fixed size pool and submit 1000 tasks to it. 3:40 how it works internally 5:30 ideal pool size for cpu task is number of cores 9:30 thread pool size for io intensive tasks

Just one suggestion, always give a link to working code, you explain well, the only thing I think missing is a link to a working code

Guys please share his videos in other groups. we have to support this kind of content and it will be very useful to people who are looking for good content

as i'm kotlin dev i just skipped this completely. But you explaining this made some things clearer. I didn't expect this.

How I wish to add the new Java 8's newWorkStealingPools() method Thanks :)

For example :: there are t1...t10 threads. Assume that at t5 exception occurs. In this case will rest of the threads execute ?

Really, so easily explained these concepts with how to implement. Superb. Should create a playlist of java 8.

Can we have two thread pools, one for io tasks and another for cpu intensive tasks?

Thanks for this clear explanation. You are doing a great job. I just wonder what is the strategy you follow to learn the concepts in crystal clear? Could you also share the resources (book, articles, docs) you follow when you were learning this topics?

Very well explained. Thanks for this. :)

Hi all i want to understand little further.. now incase of spring boot application we are not creating any executors service rite, are these created internally by application itself? As he told that DB , Network calls will utilize lot of CPU.. I have one more doubt what is process id and port num

if I have a 4 cores, I will make a thread pool of 4 size but if I want to do io (database/network call operation) task. then how I can decide to make a max number of thread pool. In your case you make the size of pool 100 for networking operation task. what if we have only 2 core or we have more than 12 cores what would we set the max size of pool?

🎯 Key Takeaways for quick navigation: 00:00 *Running tasks asynchronously in Java traditionally involves creating new threads manually.* 02:30 *Utilizing a thread pool with a fixed number of threads is more efficient than creating threads dynamically, especially for large numbers of tasks.* 04:32 *The ideal pool size depends on the nature of tasks; for CPU-intensive tasks, match the pool size to the number of CPU cores, while for IO-intensive tasks, a larger pool may be beneficial.* 08:44 *Considerations for CPU availability in multi-tasking environments and balancing thread pool size based on task submission rate and IO operation wait times are crucial for optimizing performance.*

Fantastic explaination..thanks. Can you pls share the slides of this tutorials also. Thanks!

Thanks a ton for sharing the video. Clear and concise explanation. May I ask you one question. Say If I have multi core processor and I have initialised ExecutorService with pool size as 100, all my task are IO intensive. Scheduler will make use of all core and will execute threads on different core. Is my understanding right.

Introduction: - The video discusses the concept of thread pools and the Java `ExecutorService`. - It explains how to efficiently manage tasks using a fixed number of threads. Key Points: - In Java, running tasks asynchronously is straightforward using threads. - Tasks can be executed synchronously by creating a class that implements `Runnable` and overriding the `run` method. - A new thread can be created with an instance of this class and started. - To run multiple tasks, one could use a loop to create and start new threads for each task. - However, creating too many threads can be inefficient as each thread corresponds to an operating system thread. - To address this, a thread pool can be used to manage a fixed number of threads. - Tasks can then be submitted to the thread pool, and the threads in the pool pick up and execute these tasks. - Using a thread pool reduces the overhead of creating and managing threads, improving performance. - The ideal pool size depends on factors like CPU-intensive or IO-intensive tasks. - For CPU-intensive tasks, the ideal pool size is the number of CPU cores. - For IO-intensive tasks, a larger pool size may be beneficial to handle waiting states effectively. Conclusion: - Choosing the right pool size for thread pools is crucial for optimal performance. - Understanding the nature of tasks helps determine the appropriate pool size. - Java provides the `ExecutorService` interface for managing thread pools, offering flexibility and efficiency in task execution.

if thread pool internally using blocking queue which is thread safe then how thread pool executing those task synchronously ? Because if t0 picks up the task1 so t1 can't picks up task 2 until t0 doesn't finish its work, because blocking queue is thread safe so it will not release other thread until first doesn't finish ? right ?

I watched many videos, but your video is the best till now I have watched. Can you please make videos on "Fork Join" as well ?

Very much simplified and same effective as well. +1 :)

Bro you're fucking lit. It was so easy to understand. Would definitely refer you if I could. Thanks ✌️

you explained this so clearly.....thanks for this !

Do we need any locks while using executors? bcs with executors task is executing concurrently ..Correct me if i am wrong

Why weren't you my college professor ? Thanks guru!

You are awesome, thank you for posting these videos.

Defog come back and do more videos you are the best in explaining complex concepts buddy

Awesome use of visualizations. This is really helpful, thank you!

Extremely awesome. Please keep making videos like this.

What the hell, you explain so well and clearly ! Amazing

Can you pls make videos with in-depth details on generics..I must say above videos are incredibly awesome

Please create videos on Design Patterns and SOLID Principles.

Awesome explanation.. love your work brother

Best video... Finally someone explained thread pool size derivation

Thanks for explaining in both code and internal visualization of threads. Great explanation. You have explained complicated topic in very simple way.. Thanks a lot

Awesome video... Thanks for your efforts & all

This executor service series is one of the best ever educational RU-vid series ever. Thanks a ton. Your explanation is awesome.

Lots of love and support 💖 .. one of the best explanation

Really precise to the point and very useful. You should do a podcast.

Best explanation ever, thanks for it😇😇

Thank you for clear and precise explanation. Is it useful to do multithreading on a single core processor in any way?

Very neatly explained... good work bro.. 👍🏻👍🏻

Thank you, amazing explanation!

Defog Tech! You live upto your name

Well explained, thanku so much

Why so less subscriber to such a beautiful channel , great work dude keep it up.

Very well explained, thanks!

How do we update a common shared object ( collection) by using this executorservice.

Is there a git where you maintain your code?

Could you please teach the rest of India how to speak English. You are the poster child of clear flunet English. Your pitch and clarity in the words are masterful. Also your knowledge is strong, I love the tutorial and I am as American as corn.

Very high quality explanation and accompanying slideshow. I appreciate you making this video

THANK YOU !!! A LOT OF THANKS. There is no better explanation than yours. You are the best. Keep going

awesome explanation .. really like it

do we have github location for the code

Cleared all my doubts. Thanks for this amazing video. Keep doing the great work.

Really great explanation, adding one formula for I/O intensive task, according to "Java Concurrency in Practice" Number of threads = Number of Available Cores * (1 + Wait time / Service time)

Big fan of you. Please more videos... Thank you very much.. much appreciated

Thank You Deepak bhaiya for explaing this concept so beautifully

Your way of explaining the topics are really good. I am having one question. It might be stupid one,but I wants to know How to handle the Atomicity for write and Read operation in Such case. Pool size is of 20. t1 to t20 are doing write operation. ---> They will be in waiting state t21 to t30 are doing Read operation. ---> In between any of this thread comes in and start reading and get response before completion of write operation of all 20 threads . It may get old data.

Please help me this doubt I have an API (Spring BOOT )which takes Employee ID In its service layer I'm calling 3 different external API and for this i have used multithreading by creating 3 threads to do this task. Now suppose my API is called concurrently by 100s of users how will the flow will i.e One thread per request and then having 3 threads internally doing the process OR One thread per request but bcoz of 3 threads in my service layer waiting for the thread to complete the task ?

Thanks a lot. You are amazing

The best combination of content and explanation. I wish Deepak had videos and courses on everything I need as a Java/Spring developer

explaining with how , why , what , when -------------- everything about the topic -------- hats off ----------- u will complete 100k soon bro

Hi, Thank you for the explanations I just want to understand something : The number of thred exucting an application is equals to number of available CPU cors. So, in the case we have IO tasks, and we have the risk to have all available Threds on wait status, how can the other Threads execute. Ex; for 4 available cors, 4 threds are on wait status so it's not possible to excute a fifth thread because there is only 4 available CPU cors. i am right ?

Nicely explained,👍👍👍👍, would like to see some video on design patterns from interview prospective...

good explanation but i have one doubt. you tell java thread is os thread . what do you mean by that statement?

Thank you, is there any equation for determining thread pool size approximately? Right now it seems to be computed heuristically.

Thank you so much for the content

I must tell you , your explanation on all topics are very clear and easily understandable. Thank you somuch for the vdos .. :) .. Can you please upload a vdo on React Js , If posible.

Holy Moli buddy!!! This was spot on! The BEST on the internet, cleared all my doubts right from basics to advance.. Super Thanks, I really appreciate great people like you that helps the community.

@deepakvadgama Your way of explanation is awesome. I request you if you can add some System Design Videos during lockdown days, It will help the community and your subscriber a lot. I requesting you just because your way of teaching is just awesome. watched almost all videos and learned a lot. Kindly make videos on System design concept. Thanks Himanshu

Concepts are clear and simple to understand. Thank you :)

Very good explanation.

I as individual surf youtube a lot for learning purpose and almost have watched most of the youtuber on internet, But this channel is at another level in terms of quality . Thanks a lot sir . It would be great if you could take out some time and nail the microservice buzz words

one question here, let it be an IO operation or CPU centric operation, as u said 1 java thread = new 1 OS thread, for 4 core cpu what difference it will make in creating n number of thread . irrespective of task it will only create 4 threads at a time. so for a IO operation u said we can create 100 threads. but the core size is 4. and if t0,t1,t2,t3 threads are waiting for response , how can thread scheduler gives a hand to t5 ? I am little confused here. Please help

Hi Deepak, I just watched all your 4 videos related to ExecutorService, you have shown how things can be explained in a super simple way yet powerful. Great job!! thanks.

Man .. god bless you!! Thanks!! you explain complex topics in a way anyone can understand.

explanation is good :)

Godly explanation

Great Explanation, 👍Could you please link this explanation to some Real-time scenarios(Enterprise applications)

can you share codes of program

Explained very nicely 👌

I didnt understand why there are 49 dislikes for this video? He explained very well..

Explained very well!!

Awesome explanation. This is the best i have seen so far. Looking forward to watch all your videos.

Very well explained! Thank you so much! :)

maan.....where u been all these days? Glad to find ur channel. Please make more videos.

You should post more bro. You really explain complicated topics in a really simple manner.

Hi Deepak. I have a doubt. What is the difference between server thread pool size and executor thread pool size?

All the concepts u given is aksed in an interview, best explanation ❤

Very informative!

Pleasant voice while explaning.Very clear

I have read so many places, everything is of no use, you are brilliant.

Excellent Explanation 👍

very nice exlaination.

Hi, Can you please help me understand why wait() notify has to call inside while loop

Beautiful explanation

Thanks for the wonderful explanation.