Surprisingly, IPython sends one message per engine per command between the controller and the client. The controller then routes each one of these messages to the appropriate engine.
This has a potential to be a large bottelneck, for example if you want to push a large piece of data to the engines. It will be copied N times and push through the single channel between the controller and client.
Surprisingly, IPython sends one message per engine per command between the controller and the client. The controller then routes each one of these messages to the appropriate engine.
This has a potential to be a large bottelneck, for example if you want to push a large piece of data to the engines. It will be copied N times and push through the single channel between the controller and client.