--
You received this message because you are subscribed to the Google Groups "fireworkflows" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fireworkflow...@googlegroups.com.
To post to this group, send email to firewo...@googlegroups.com.
Visit this group at https://groups.google.com/group/fireworkflows.
To view this discussion on the web visit https://groups.google.com/d/msgid/fireworkflows/11f9fa81-6d95-4273-b1ab-e8661aa72cd8%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Hi Roman,If you are running on a single machine, typically you want to just use a single Worker unless you have different job types and want the same machine to handle two different categories of jobs differently. In your case, I think you want to keep a single Worker but use the multi-launch:Let me know if it doesn't solve your problemBest,Anubhav
On Wed, Mar 30, 2016 at 9:44 PM, Roman M <roma...@gmail.com> wrote:
Stumbled upon Fireworks today, and have a newbie question. Thanks in advance.I have eight cores on my machine, my workflow has a diamond shape. I first split work into 1000 tasks, calculate 1000 in parallel and then join the results together. I don't quite understand, where I specify the number of concurrent workers, I want to set it to 8.If someone can point me to an example in python, that would be great.-Roman
--
You received this message because you are subscribed to the Google Groups "fireworkflows" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fireworkflows+unsubscribe@googlegroups.com.
--
You received this message because you are subscribed to the Google Groups "fireworkflows" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fireworkflow...@googlegroups.com.
To post to this group, send email to firewo...@googlegroups.com.
Visit this group at https://groups.google.com/group/fireworkflows.
To view this discussion on the web visit https://groups.google.com/d/msgid/fireworkflows/45421449-9be9-4c60-9ad3-176847844136%40googlegroups.com.
Hi Nick,Sorry for the confusion. Usually we are careful in the docs to properly distinguish Firework vs workflow. In this case, the docs were written a bit sloppily.The parallelization is over Fireworks, which can be either within the same Workflow or across several Workflows. Each parallel worker just pulls available (=READY) Fireworks and runs them regardless of what Workflow they are in.I will update the docs soon to be more clear.Best,Anubhav
On Fri, Apr 15, 2016 at 9:04 AM, Nick Vandewiele <nickvan...@gmail.com> wrote:
Hi,I am a bit confused about what can be parallelized and what not through the mlaunch application:The documentation mentions that independent workflows can be parallelized, whereas the reply by Anubhav suggests that individual Fireworks are run in parallel, when the structure of the workflow permits it.Should I interpret the term workflow and firework as interchangeable here?Thanks!
On Thursday, March 31, 2016 at 12:44:01 AM UTC-4, Roman M wrote:Stumbled upon Fireworks today, and have a newbie question. Thanks in advance.I have eight cores on my machine, my workflow has a diamond shape. I first split work into 1000 tasks, calculate 1000 in parallel and then join the results together. I don't quite understand, where I specify the number of concurrent workers, I want to set it to 8.If someone can point me to an example in python, that would be great.-Roman
--
You received this message because you are subscribed to the Google Groups "fireworkflows" group.
To unsubscribe from this group and stop receiving emails from it, send an email to fireworkflows+unsubscribe@googlegroups.com.
To post to this group, send email to firewo...@googlegroups.com.
Visit this group at https://groups.google.com/group/fireworkflows.