59

Does anyone know if there is any difference between doing Task.Factory.StartNew vs new Task followed by calling Start on the task. Looking at reflector there doesn't seem to be much difference. So perhaps the only difference is that Task.Factory.StartNewreturns a task that is already started. Is this correct?

I know that Task.Factory.StartNewand Task.Run have different default options and Task.Run is the preferred option for .Net 4.5.

2 Answers 2

58

I found this great article by Stephen Toub, which explains that there is actually a performance penalty when using new Task(...).Start(), as the start method needs to use synchronization to make sure the task is only scheduled once.

His advice is to prefer using Task.Factory.StartNew for .net 4.0. For .net 4.5 Task.Run is the better option.

Sign up to request clarification or add additional context in comments.

3 Comments

Sometimes (rarely) you may need to use Task constructor, e.g: stackoverflow.com/q/21424084/1768303
More confirmation of preference to Task.Run by @StephenCleary here
Updated link for someone who wants to read the article - devblogs.microsoft.com/pfxteam/…
17

Actually in the article by Stephen Toub he specifies that Task.Run() is exactly equivalent to using Task.Factory.StartNew() with the default parameters:

Task.Factory.StartNew(someAction, CancellationToken.None, TaskCreationOptions.DenyChildAttach, TaskScheduler.Default); 

1 Comment

Not exactly equivalent when it comes to async. As Stephen Toub explains. This has tripped me up before

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.