Whit is the different between Task vs Thread?

Question

Whit is the different between Task vs Thread

Sundar · Answer

Thread is a lower-level concept: if you're directly starting a thread you know it will be a separate thread rather than executing on the thread pool etc. Task is more than just an abstraction of where to run some code though - it's really just the promise of a result in the future. So as some different examples: Task.Delay doesn't need any actual CPU time; it's just like setting a timer to go off in the future A task returned by WebClient.DownloadStringTaskAsync won't take much CPU time locally; it's representing a result which is likely to spend most of its time in network latency or remote work (at the web server) A task returned by Task.Run() really is saying I want you to execute this code separately; the exact thread on which that code executes depends on a number of factors.

Rajkiran Swain · Answer

http://blog.slaks.net/2013-10-11/threads-vs-tasks/

Manikandan Murugesan · Answer

For Further Reference Refer the following Link : https://social.msdn.microsoft.com/Forums/en-US/54046785-55c3-41ce-bfa9-847ff67ed658/difference-between-threads-and-tasks?forum=async

Manikandan Murugesan · Answer

When we execute things on multiple threads it’s not guaranteed that the threads are separated across multiple processors. Task is a lightweight object for managing a parallelizable unit of work. It can be used whenever you want to execute something in parallel. Parallel means the work is spread across multiple processors to maximize computational speed. Tasks are tuned for leveraging multicores processors. Task provides following powerful features over thread. If system has multiple tasks then it make use of the CLR thread pool internally and so do not have the overhead associated with creating a dedicated thread using the Thread. Also reduce the context switching time among multiple threads. Task can return a result. There is no direct mechanism to return the result from thread. Wait on a set of tasks without a signaling construct. We can chain tasks together to execute one after the other. Establish a parent/child relationship when one task is started from another task. Child task exception can propagate to parent task. Task support cancellation through the use of cancellation tokens. Asynchronous implementation is easy in task using’ async’ and ‘await’ keywords.