title: Advantage of using Thread.Start vs QueueUserWorkItem
body: <p>In multithreaded .NET programming, what are the decision criteria for using ThreadPool.QueueUserWorkItem versus starting my own thread via new Thread() and Thread.Start()?  </p>
  
  <p>In a server app (let's say, an ASP.NET app or a WCF service)  I think the ThreadPool is always there and available.   What about in a client app, like a WinForms or WPF app?  Is there a cost to spin up the thread pool?  If I just want 3 or 4 threads to work for a short period on some computation, is it better to QUWI or to Thread.Start(). </p>