[kepler-users] Python Actor is not running in parallel under PN Director

[Edward A. Lee]

This has come up before.
The Python actor shares a single Python interpreter
and serializes your two sleep operations...

Edward


Daniel Korytina wrote:
> Hello,
> 
> I am striving for some simple parallel execution, but I'm not sure why its not working.
> 
> My workflow has:
> 1. PN director
> 2. Python Actor (which runs random sleep(), 0-5 seconds)
> 
> Because the Python actor uses time.sleep(), it has virtually 0% processor load.
> 
> - I've timed it with the PN Director, then replaced the PN Director with an SDF Director. But the speed is practically identical. 
> 
> Here's the workflow I'm referring to (very simple):
> http://sites.google.com/site/korytina/kepler-files/random_sleep.xml
> 
> Q: Is there a simple way to run multiple copies of Python to get faster execution time?
> 
> Thank you,
> Daniel
> _______________________________________________
> Kepler-users mailing list
> Kepler-users at kepler-project.org
> http://mercury.nceas.ucsb.edu/kepler/mailman/listinfo/kepler-users
-------------- next part --------------
A non-text attachment was scrubbed...
Name: eal.vcf
Type: text/x-vcard
Size: 351 bytes
Desc: not available
URL: <http://lists.nceas.ucsb.edu/kepler/pipermail/kepler-users/attachments/20090731/8435e68c/attachment.vcf>