title: ThreadPool vs dedicated Thread - when to prefer which
body: <p>Is there any way (apart form actual perfomance measurements which can be pretty hard to make them realistic) or rule of thumb when I should stop using the <code>ThreadPool</code> and use a dedicated <code>Thread</code> instead? I suppose for long running work it is better to use a dedicated <code>Thread</code> because it doesn't peramently steal one from the <code>ThreadPool</code>. For shorter work it is better use the the <code>ThreadPool</code> because creating threads and the thread itself consumes a lot of resources.</p>
  
  <p>But where is the magic barrier? How do I decide which approach to use?</p>
  
  <p>In simple applications it might not matter that much. But I am dealing with a custom .NET-based application framework where a single application can have a <em>lot</em> of plugins which in most cases need to do some work asynchonously. And I am thinking about introducing a policy for the plugin authors when to use which.</p>