This is very tricky way to teach something very effectively. @Clint Eastwood you r a great teacher, i just love the way you teach and i'm pretty sure that i won't forget this TPL lesson. Some people can understand well but they can't teach well , here you r both way perfect . May god bless u.
Thank you so much, this video is instrumental in helping me understand Parallel Programming. You're a great communicator who can explain a complicated subject so clearly that I can truly visualize the simultaneous running of tasks.
Great article, very well explained. Thank you heaps, I'm now using this TPL instead of the old threading. You're a great teacher and explains the topic in a clear, simple to understand manner. I'll be subscribing in your channel.
Task.Waitall takes vararg, you can see the params keyword in there at 15:56, so there is no need create a new list of Task which you created at 16:20. You are just adding noise to your code. You can simply send all the tasks like this: Task.WaitAll(t1, t2, t3);
Hi Gary, WaitAll & WaitAny takes array as parameters, he may have skipped creating a list, but in normal cases we have them as list and convert to array for waitAll purpose. msdn.microsoft.com/en-us/library/system.threading.tasks.task.waitall(v=vs.110).aspx
Thnx... i did not knew about Parallel is stopping the execuation until its operation is over.. Gr8 work... i would prefer to use tasks instead of threads now.... :)
Thread: If your application has to do something important through out the application(or something that has to really reliable). Thread from the threadpool (Task): If you want to get something quick and running without blocking your UI.
Manish Aryal There is a difference between using "Thread" and "Task". The thread you get from task is borrowed from the thread pool your OS has reserved for you.
I don't understand the part where you compared Thread and Task, and stated that the Thread is more reliable? I mean, how? What sense? I don't think there is much difference instead for few trivial ones? If I'm wrong, please do correct me. :)
Manish Aryal If you want something to run throughout your application use a thread. Because when you use task you are just taking a thread from the thread pool. Where as a "Thread" creates a OS level thread. Like for say a "Thread" has its own stack an kernel where as a thread from "Task" does not. You cant it here excellent article. blog.slaks.net/2013-10-11/threads-vs-tasks/
Do not use Thread.Sleep inside a task. This can be a problem if you're running more tasks than threads in your cpu by unnecessarily blocking your thread. Instead use await Task.Delay(int).
Wonder what happens if a parallel.foreeach was inside a task, that quickly made http requests, but the task gets cancelled by a token? What happens to the request items which haven't returned during the ForEach?
i don't understand what you mean by you didn't stop it fast enough .. i don't understand why did it continue on executing when the Catch console message was written first ?? or maybe you mean that the task has passed the if condition then the cancel method redid the if condition again ? can anyone explain this
of course you can't change the Boolean value once it is passed as a parameter but on the other hand cancellation token's value can be change any time. Think if Task as some kind of loop going on (maybe infinite loop) and on each iteration cancellation token is been checked so you can cancel that task only with token by changing its value anytime
Good video! How do you remote logon with uid and password to a windows server in the code..and execute external application commands on multiple hosts in parallel using C# ? I can do this in Unix systems using cshell, awk, etc. but I'd like to do this from a WPF using C#. Any tips?
+Don'tBeEvil I believe it is because the System.Threading.Tasks library takes time to load and the 2nd task is fired quicker on the new thread than it takes the application to load the library and fire the first one. Basically, there is a cost to load the task library which is paid upfront by the first instance of it in the application.
Two thirds through this video, I am looking to see that we're near the end. Oh. We're not near done yet. Please do, tell me more. (SUBSCIBE + like = That is all.) Thank you Clint Eastwood. I'm 1 vid in and a super fan already.
it bad when you can write if statements and know what your input will always be... When you are working with data and transferring of data and one bad record break you want to continue the execution minus the bad record...how does one do that without try and catch? Sit down and test the whole day and figure out what the data issue was? or do a try and catch and skip the bad data? If am writing a code and i see there is 2% data loss why not do that than trying figure out all that problem then realize you still cant fix it? IT DEPENDS MY G.
Why is it that so many of these videos are so overintroduced? Do their makers seriously think somebody randomly clicks the video and needs to be explained what it's about and get enticed into watching any further? There's no need for two and a half minutes of warm up and historical context...
Sometimes the BEST things in life are FREE!
Thanks for the awesome explanation, it really rocks! 👆
Its not free, you are viewing ads :D or you have youtube premium subscription. Someway or the other you are paying.
It's amazing how simply one can explain complicated things. Great playlist !!!
This is very tricky way to teach something very effectively. @Clint Eastwood you r a great teacher, i just love the way you teach and i'm pretty sure that i won't forget this TPL lesson. Some people can understand well but they can't teach well , here you r both way perfect . May god bless u.
Thank you so much, this video is instrumental in helping me understand Parallel Programming. You're a great communicator who can explain a complicated subject so clearly that I can truly visualize the simultaneous running of tasks.
You explain things very well and I appreciate that you use easy to medium code complexity. You explaining what you are doing is useful.
The best presentation tasks and parallel programming so far. Thank you very much for the excellent work you saved me a lot of time.
What a great tutor you are. I love the confidence of showing things out. Great work :)
Great article, very well explained.
Thank you heaps, I'm now using this TPL instead of the old threading. You're a great teacher and explains the topic in a clear, simple to understand manner. I'll be subscribing in your channel.
Very clearly explained and good demos to show the concept working. Nice job!
Really helpfull for me.I learned 3 new things in c#.Thanks a lot
Really superb content. Very nice way explain TPL term. Really appreciate efforts.
Task.Waitall takes vararg, you can see the params keyword in there at 15:56, so there is no need create a new list of Task which you created at 16:20. You are just adding noise to your code. You can simply send all the tasks like this:
Task.WaitAll(t1, t2, t3);
Hi Gary, WaitAll & WaitAny takes array as parameters, he may have skipped creating a list, but in normal cases we have them as list and convert to array for waitAll purpose.
msdn.microsoft.com/en-us/library/system.threading.tasks.task.waitall(v=vs.110).aspx
the guy used List to teach in parallel (pun not intended) the viewers on what to do when you have a lot task objects
simple & clean way of teaching a concept , good work!
Very clear and well explained. A great introduction to TPL. Thanks for sharing!
A best video to understand TPL concept in C# :)
Like the way you explain concept practically.
Thnx... i did not knew about Parallel is stopping the execuation until its operation is over.. Gr8 work... i would prefer to use tasks instead of threads now.... :)
Outstanding tutorial, thumbs up !!
Thank you so much for very simple and efficient explanation.
Beautifully relayed..thank you!
Thank you so much. its awesome. better than threading. kindly make a video on GUI tasks.
Thanks!!! It is very clear to understand
Very well detailed tutorial on TPL thanks for this
Very nice tutorial, gonna check this series out...
Thread: If your application has to do something important through out the application(or something that has to really reliable).
Thread from the threadpool (Task): If you want to get something quick and running without blocking your UI.
huh?
Manish Aryal There is a difference between using "Thread" and "Task". The thread you get from task is borrowed from the thread pool your OS has reserved for you.
I don't understand the part where you compared Thread and Task, and stated that the Thread is more reliable? I mean, how? What sense? I don't think there is much difference instead for few trivial ones?
If I'm wrong, please do correct me. :)
Manish Aryal If you want something to run throughout your application use a thread. Because when you use task you are just taking a thread from the thread pool. Where as a "Thread" creates a OS level thread. Like for say a "Thread" has its own stack an kernel where as a thread from "Task" does not. You cant it here excellent article. blog.slaks.net/2013-10-11/threads-vs-tasks/
Do not use Thread.Sleep inside a task. This can be a problem if you're running more tasks than threads in your cpu by unnecessarily blocking your thread. Instead use await Task.Delay(int).
This video is so great! Thanks for sharing!
Great Video. Thank you for posting.
best thread video!!
Wonder what happens if a parallel.foreeach was inside a task, that quickly made http requests, but the task gets cancelled by a token? What happens to the request items which haven't returned during the ForEach?
How can i check how many threads i have on my computer in c# and calculate best option to perform some task, like multiply 2 matrix ?
Really nice stuff
i don't understand what you mean by you didn't stop it fast enough .. i don't understand why did it continue on executing when the Catch console message was written first ?? or maybe you mean that the task has passed the if condition then the cancel method redid the if condition again ? can anyone explain this
Amazing video, thank you very much
Does it create a new thread each time you create a task?
Many useful!
Many thanks!
This is really a nice video to understand Thread parallel processing. Can you please post the link to the thread pooling video
Good explaination :)
what's the difference if I use a bool flag instead of cancellationtoken?
of course you can't change the Boolean value once it is passed as a parameter but on the other hand cancellation token's value can be change any time. Think if Task as some kind of loop going on (maybe infinite loop) and on each iteration cancellation token is been checked so you can cancel that task only with token by changing its value anytime
What if I want multiple tasks to be able to read and write the same variables ? how would I deal with a situation like that ?
Thank you for such a nice video. My doubt is after we throw exception from the DoImpWork, Why the exception is not getting caught?
Great video!
Can I use continuewith to run the same method?
Where does the prevTask variable get it's value from? Or rather how?
Well explained !!!
Good video! How do you remote logon with uid and password to a windows server in the code..and execute external application commands on multiple hosts in parallel using C# ? I can do this in Unix systems using cshell, awk, etc. but I'd like to do this from a WPF using C#. Any tips?
Please can you share a video on Task.Factory.FromAsync() method?
Awesome!!.
11:11 Why Task 2 is started first?! not Task 1?
+Don'tBeEvil I believe it is because the System.Threading.Tasks library takes time to load and the 2nd task is fired quicker on the new thread than it takes the application to load the library and fire the first one. Basically, there is a cost to load the task library which is paid upfront by the first instance of it in the application.
thank you!
Thank you so much.
Thanks!
Thanks
Rather than throwing an exception you could have returned from that method. Not in every case but that case.
thanks for TPL crash course :)
It almost looks like you are doing more than one thing at the same time.. O.O *gasp* imagine that... lol
Interesting yes.
Confusing also yes.
This is slightly confusing. I think il have to watch this vid a few times.
we explained.10/10
pretty good.
Two thirds through this video, I am looking to see that we're near the end. Oh. We're not near done yet. Please do, tell me more. (SUBSCIBE + like = That is all.) Thank you Clint Eastwood. I'm 1 vid in and a super fan already.
I thought that using exceptions to do operations is bad practice, isn't that what you are doing here? Using exception in order to stop the task.
it bad when you can write if statements and know what your input will always be...
When you are working with data and transferring of data and one bad record break you want to continue the execution minus the bad record...how does one do that without try and catch?
Sit down and test the whole day and figure out what the data issue was? or do a try and catch and skip the bad data?
If am writing a code and i see there is 2% data loss why not do that than trying figure out all that problem then realize you still cant fix it?
IT DEPENDS MY G.
why do people prefer startnew while others prefer task.run
CarouselBlind did you get any answer for your question why people use startnew while others use task.run?
you save one line of code
i cried
why ?
Why is it that so many of these videos are so overintroduced? Do their makers seriously think somebody randomly clicks the video and needs to be explained what it's about and get enticed into watching any further? There's no need for two and a half minutes of warm up and historical context...
is that you at docs.microsoft articles? I saw there John Doe lol
Great video!!!
Is it ok to pull records from database using TPL. Can it cause issue in web api?