- 
                Notifications
    You must be signed in to change notification settings 
- Fork 61
Experiment with threadpools #113
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
          
     Open
      
      
            SylvainCorlay
  wants to merge
  1
  commit into
  jupyter:main
  
    
      
        
          
  
    
      Choose a base branch
      
     
    
      
        
      
      
        
          
          
        
        
          
            
              
              
              
  
           
        
        
          
            
              
              
           
        
       
     
  
        
          
            
          
            
          
        
       
    
      
from
SylvainCorlay:experiment-with-threadpools
  
      
      
   
  
    
  
  
  
 
  
      
    base: main
Could not load branches
            
              
  
    Branch not found: {{ refName }}
  
            
                
      Loading
              
            Could not load tags
            
            
              Nothing to show
            
              
  
            
                
      Loading
              
            Are you sure you want to change the base?
            Some commits from the old base branch may be removed from the timeline,
            and old review comments may become outdated.
          
          
  
     Open
                    Changes from all commits
      Commits
    
    
  File filter
Filter by extension
Conversations
          Failed to load comments.   
        
        
          
      Loading
        
  Jump to
        
          Jump to file
        
      
      
          Failed to load files.   
        
        
          
      Loading
        
  Diff view
Diff view
There are no files selected for viewing
  
    
      This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
      Learn more about bidirectional Unicode characters
    
  
  
    
              | Original file line number | Diff line number | Diff line change | 
|---|---|---|
|  | @@ -6,6 +6,8 @@ | |
| import asyncio | ||
| import sys | ||
| import inspect | ||
| import concurrent.futures | ||
|  | ||
| from typing import Callable, Awaitable, Any, Union | ||
|  | ||
|  | ||
|  | @@ -28,6 +30,7 @@ def check_patch_tornado() -> None: | |
| tornado.concurrent.FUTURES = \ | ||
| tornado.concurrent.FUTURES + (asyncio.Future, ) # type: ignore | ||
|  | ||
| pool = concurrent.futures.ThreadPoolExecutor() | ||
|  | ||
| def just_run(coro: Awaitable) -> Any: | ||
| """Make the coroutine run, even if there is an event loop running (using nest_asyncio)""" | ||
|  | @@ -44,14 +47,9 @@ def just_run(coro: Awaitable) -> Any: | |
| else: | ||
| had_running_loop = True | ||
| if had_running_loop: | ||
| # if there is a running loop, we patch using nest_asyncio | ||
| # to have reentrant event loops | ||
| check_ipython() | ||
| import nest_asyncio | ||
| nest_asyncio.apply() | ||
| check_patch_tornado() | ||
| return loop.run_until_complete(coro) | ||
|  | ||
| return pool.submit(asyncio.run, coro).result() | ||
| There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. We could have only this line in the function, so that we always run in a thread with its own event loop. | ||
| else: | ||
| return loop.run_until_complete(coro) | ||
|  | ||
| def run_sync(coro: Callable) -> Callable: | ||
| """Runs a coroutine and blocks until it has executed. | ||
|  | ||
  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.
  
    
  
    
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Any reason to use more than one thread? I think we should use
max_workers=1.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
max_worker should be fine IMO.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you don't specify
mar_workers, it will use unnecessary resources: "If max_workers is None or not given, it will default to the number of processors on the machine, multiplied by 5".Since you never actually run concurrently, you don't need more than 1 thread.