Mon Apr 23 14:03:30 CDT 2012
ps. the reason i couldn't make it another task is because of the
>> distributed context. the engine on which the dependent task runs cannot be
>> controlled (i think).
> Nope. The engines can be controlled quite specifically.
> LoadBalancedViews have a 'targets' attribute, just like DirectViews, but
> they select which *subset* of targets across which the tasks may be
> distributed. If this is a single engine, then you know exactly where it
> will run.
this is more academic at this point, but just to be clear on the
i have X engines running on X machines. and i'm distributing a task to some
arbitrary engine using LoadBalancedView. is there a way for me to send task
A and B and say run B on the same engine as A. if i remember target
attributes were setup during creation of an engine? i don't want to run A
on any particular engine.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the IPython-dev