Update executors.py #2
                
     Merged
            
            
          
  Add this suggestion to a batch that can be applied as a single commit.
  This suggestion is invalid because no changes were made to the code.
  Suggestions cannot be applied while the pull request is closed.
  Suggestions cannot be applied while viewing a subset of changes.
  Only one suggestion per line can be applied in a batch.
  Add this suggestion to a batch that can be applied as a single commit.
  Applying suggestions on deleted lines is not supported.
  You must change the existing code in this line in order to create a valid suggestion.
  Outdated suggestions cannot be applied.
  This suggestion has been applied or marked resolved.
  Suggestions cannot be applied from pending reviews.
  Suggestions cannot be applied on multi-line comments.
  Suggestions cannot be applied while the pull request is queued to merge.
  Suggestion cannot be applied right now. Please check back later.
  
    
  
    
The class TascQueue accepts an argument
thread_countthat is used for the max size of a queue.In the
MultithreadedJobExecutorclass there is a variable defined (max_cores) that is getting its value from the available cores of the machine. Further down in the same class when TaskQueue is called instead of using themax_coresit is usingpsutil.cpu_count().I suggest to use the self.max_cores in the call of TaskQueue in the file executor.py instead of psutil.cpu_count()
Use case:
when a job executor is setup as MultithreadedJobExecutor one can override the max_cores after the initialization of the object and limit the use to the specified cores.
Additional enhancement would be to include an argument to allow the use to provide the number of cores available for use