title: What kind of problems (if any) would there be combining asyncio with multiprocessing?
body: <p>As almost everyone is aware when they first look at threading in Python, there is the GIL that makes life miserable for people who actually want to do processing in parallel - or at least give it a chance.</p>
  
  <p>I am currently looking at implementing something like the Reactor pattern. Effectively I want to listen for incoming socket connections on one thread-like, and when someone tries to connect, accept that connection and pass it along to another thread-like for processing.</p>
  
  <p>I'm not (yet) sure what kind of load I might be facing. I know there is currently setup a 2MB cap on incoming messages. Theoretically we could get thousands per second (though I don't know if practically we've seen anything like that). The amount of time spent processing a message isn't <em>terribly</em> important, though obviously quicker would be better.</p>
  
  <p>I was looking into the Reactor pattern, and developed a small example using the <code>multiprocessing</code> library that (at least in testing) seems to work just fine. However, now/soon we'll have the <a href="http://docs.python.org/3.4/library/asyncio.html">asyncio</a> library available, which would handle the event loop for me.</p>
  
  <p>Is there anything that could bite me by combining <code>asyncio</code> and <code>multiprocessing</code>?</p>