Why can EngineThreads property on the data-flow task not equal 1?

Why can EngineThreads property on the data-flow task not equal 1?

• Alan Hsiao

  If we did would you ask why we allow it to be 1 :)
  
  Since EngineThreads is just a suggestion it was determined that 1 would almost never be acceptable for the threading algorithm so we would almost never be able to use that suggestion so why allow it (so I guess you could argue, just like 5 being the default, it was arbitrary).  Also, you should be aware that we never create more threads than we need so if you set it to 100 and the algorithm determined it needed 1 then only 1 thread would be created.
  
  Matt
  
  

• mashti

  Matt David wrote:

  If we did would you ask why we allow it to be 1 :) Since EngineThreads is just a suggestion it was determined that 1 would almost never be acceptable for the threading algorithm so we would almost never be able to use that suggestion so why allow it (so I guess you could argue, just like 5 being the default, it was arbitrary).  Also, you should be aware that we never create more threads than we need so if you set it to 100 and the algorithm determined it needed 1 then only 1 thread would be created. Matt

  
  
  So EngineThreads property is pointless then
  
  Thanks for the reply Matt!
  
  -Jamie
  
  
  

• Margie from Seattle

  Actually here's another question.
  
  What's the differrence between a source thread and a worker thread And when does a source thread become a worker thread
  
  I doubt I'm ever going to NEED to know but it'd be nice to know anyway, y'know.
  
  -Jamie
  
  
  

• Karthik R181134

  There's no better answer than the pipeline engine simply needs at least 2 threads to function correctly. Matt can give a more precise answer, but I think one thread is needed for the buffer manager and the other for execution.
  K
  
  
• Why can EngineThreads property on the data-flow task not equal 1?