Skip to main content
  • EN

Hello Group,

 

I'm experimenting with WorkspaceRunner. I've noticed that when I run a workspace via WorkspaceRunner the workspace itself completes far faster than if I ran the workspace directly. For example I have one workspace that processes around 20 heavy datasets and usually takes around 10-15 minutes to complete. But via WorkspaceRunner it takes just seconds.

 

Or am I just misunderstanding WoprkspaceRunner. Is it actually the case that WorkspaceRunner itself completes quickly but the actual workspace/s it has fired off continues independently and takes just as long as if running directly? 

 

Thanks,

Stuart

 

 

There is a setting in the WorkspaceRunner transformer Wait for job to complete. If this is set to no, FME will initiate up to 7 processes running the child workspace concurrently, making it appear as if it's completing faster than it actually is. I'm guessing this is what you are seeing. Try setting this parameter to Yes, and see if there is a difference.

 

Otherwise, I'd say you've found the holy grail of efficiency 😎 (Or a bug in the software 😂 )

There is a setting in the WorkspaceRunner transformer Wait for job to complete. If this is set to no, FME will initiate up to 7 processes running the child workspace concurrently, making it appear as if it's completing faster than it actually is. I'm guessing this is what you are seeing. Try setting this parameter to Yes, and see if there is a difference.

 

Otherwise, I'd say you've found the holy grail of efficiency 😎 (Or a bug in the software 😂 )

Thanks for that. Setting to Yes has made the difference.

Thanks,

Reply


Community Stats

29,994
Posts
113,939
Replies
37,621
Members
Terms & ConditionsCookie settings