title: What does setting Thread.Priority = Lowest really mean?
body: <p>In an effort to speed up the startup of my resource-hungry app, I've moved various startup tasks to background threads and marked those thread with 'Thread.Priority = Lowest`.</p>
  
  <p>However, those low priority threads still execute pretty much in parallel with the application (as it loads its UI), as evidenced by the timeline on the ANTS Profiler.  My understanding was that Lowest meant that the CPU will handle all higher priority threads first, then get the lower priority threads.</p>
  
  <p>Is my understanding flawed?</p>