Thanks a lot for this series. I have 2 questions: 1) at after line 22 and before running the task, ideally shouldn't you call "condition.notify_one();"? With the code as it is in the video it seems that the other thread's "condition.wait" will run spuriously instead of being notified. 2) your main() function creates a thread pool, enqueues some tasks but then returns 0 right away. I don't understand how your threads are doing work since the thread pool is destroyed instantly. Thanks!
Thank you for the tutorial. I would like to know how one could receive the return value of a task or wait for a specific task to finish before proceeding.
Thanks, nice video! During this video I got stuck in an endless loop while learning about capture clauses in lamdas, std::function, move, forward, default, delete and probably a couple more while watching this video 😅 I had too many gaps. actually, I landed in this playlist cuz I got stuck in one such loops and my stack has now definitely overflowed and I don't even remember what I was studying in the first place... I was studying caching but I don't even remember how I ended up here.
Thank you for this video, it's very interesting! I have a question: is there a way to know when all the threads have completed their work so that the main thread can wait? Thank you.
The current code will wait for all the work to finish then only it will terminate. Because termination is written in Destructor it will start the destroying when return 0; is hit. But in thread if you see there is a check (stop && tasks.empty ()) this will not allow to return from thread if tasks queue is not empty. I will paste the current code link you can run and check it will br very helpful.
I admire you for sharing this content with us. I have some question marks regarding the use of locks and std::function Thanks a lot. 1 - Why you acquired the mutex in the desctructor? I could not see the point since no thread is modifying the stop flag. Tried 8 threads and 1,6 milion of tasks, worked perfectly fine without the mutex acquisition. 2 - Also didnot see the point to use unlock() in the enqueue() function. Removed it. Still works totally fine. 3 - In the enqueue() function, I did not get the idea of using template. Since the type of the workers is std::queue, it cannot get other signatured invokable objects than void(), no? I tried to pass a lambda with the signature of void(int), it failed. So what is the point of the template?
The inner loop will never end till the program is running. Pools are like we keep them running for any incoming jobs, and jobs can come anytime hence we have to keep on waiting state for the job. Please read about conditional variable then you will know what is happening.
Why does every TH-cam thumbnail now have the host with either their mouth open in the O-shape or a finger on their lips? Does the TH-cam algorithm give an extra push to such videos now? Humanity now seems to be on an intellectual race to the bottom! No complaints about the content of this video. Great one, thanks brother!
I thought let's just do what others are doing may be they are doing for some reason 😬 I never did the research.. 🙃 Thanks for putting thoughts on this, I also feel the same way now.
the workers vector is of type thread, it pushes new threads with dedicated function. std::thread accepts function as its 1st argument. so when we emplace_back a new thread object, we implicitly declare a new thread object, and give a lambda function as its 1st argument to the new thread inside vector.
I am sorry for making you feel that way. But Thread Pool is little complex which require many basic concepts should be clear. (mutex and condition_variable, function pointer etc..)
You are so good at explaining the code. This video is really helpful. Appreciate your time and effort to create this video!
Thank so much for making understanding each and every line of code along with OS concept😊😊
Thanks a lot for this series. I have 2 questions:
1) at after line 22 and before running the task, ideally shouldn't you call "condition.notify_one();"? With the code as it is in the video it seems that the other thread's "condition.wait" will run spuriously instead of being notified.
2) your main() function creates a thread pool, enqueues some tasks but then returns 0 right away. I don't understand how your threads are doing work since the thread pool is destroyed instantly.
Thanks!
Thank you for the tutorial. I would like to know how one could receive the return value of a task or wait for a specific task to finish before proceeding.
promise And future In C++
th-cam.com/video/XDZkyQVsbDY/w-d-xo.html
This is the way..
I love your every video. thanks for making videos
Can you please make few videos on how to communicate with DB like Oracle SQL in cpp?
This will take time maybe..
Good explanation and highly appreaciated.
Glad it was helpful!
Finally we saw you 😊
excellent video. very clear
Thanks, nice video!
During this video I got stuck in an endless loop while learning about capture clauses in lamdas, std::function, move, forward, default, delete and probably a couple more while watching this video 😅
I had too many gaps.
actually, I landed in this playlist cuz I got stuck in one such loops and my stack has now definitely overflowed and I don't even remember what I was studying in the first place... I was studying caching but I don't even remember how I ended up here.
So did you finally understood ?
@@CppNuts had taken a while to go through everything but yes!
Thank you for this video, it's very interesting! I have a question: is there a way to know when all the threads have completed their work so that the main thread can wait? Thank you.
The current code will wait for all the work to finish then only it will terminate.
Because termination is written in Destructor it will start the destroying when return 0; is hit.
But in thread if you see there is a check (stop && tasks.empty ()) this will not allow to return from thread if tasks queue is not empty.
I will paste the current code link you can run and check it will br very helpful.
@@CppNuts Thank you!
I admire you for sharing this content with us. I have some question marks regarding the use of locks and std::function Thanks a lot.
1 - Why you acquired the mutex in the desctructor? I could not see the point since no thread is modifying the stop flag. Tried 8 threads and 1,6 milion of tasks, worked perfectly fine without the mutex acquisition.
2 - Also didnot see the point to use unlock() in the enqueue() function. Removed it. Still works totally fine.
3 - In the enqueue() function, I did not get the idea of using template. Since the type of the workers is std::queue, it cannot get other signatured invokable objects than void(), no? I tried to pass a lambda with the signature of void(int), it failed. So what is the point of the template?
Thank Bro ❤
when will the inner infinite loop end? and when will the next threads get created? I am not able to understand.
The inner loop will never end till the program is running.
Pools are like we keep them running for any incoming jobs, and jobs can come anytime hence we have to keep on waiting state for the job.
Please read about conditional variable then you will know what is happening.
Why does every TH-cam thumbnail now have the host with either their mouth open in the O-shape or a finger on their lips? Does the TH-cam algorithm give an extra push to such videos now? Humanity now seems to be on an intellectual race to the bottom!
No complaints about the content of this video. Great one, thanks brother!
I thought let's just do what others are doing may be they are doing for some reason 😬 I never did the research.. 🙃
Thanks for putting thoughts on this, I also feel the same way now.
awesome, now I'm gonna build my own game engine LOL
Why vector worker has not type of function, as we are pushing lambda function to it
the workers vector is of type thread, it pushes new threads with dedicated function.
std::thread accepts function as its 1st argument.
so when we emplace_back a new thread object,
we implicitly declare a new thread object, and give a lambda function as its 1st argument to the new thread inside vector.
You make things complex unnecessarily. I see many places where things could have been easily simplified for beginners.
I am sorry for making you feel that way.
But Thread Pool is little complex which require many basic concepts should be clear. (mutex and condition_variable, function pointer etc..)
Thanks for the nice content, where is the source code for the same video. Can you share it, what is the process to get the code for videos?
Thanks
Plz check channel about page. You will get the link of git hub
Please Explain MFC