Skip to main content
Solved

WorkspaceRunner completion times

  • December 22, 2022
  • 2 replies
  • 50 views
scarter
Contributor
Forum|alt.badge.img+10

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

 

 

Best answer by dustin

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 😂 )

This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.

2 replies

dustin
Influencer
Forum|alt.badge.img+31
  • dustinInfluencer
  • Influencer
  • 627 replies
  • Best Answer
  • December 22, 2022

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 😂 )

scarter
Contributor
Forum|alt.badge.img+10
  • scarterContributor
  • Author
  • Contributor
  • 125 replies
  • December 22, 2022

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,

Community Stats

32,066
Posts
121,745
Replies
39,692
Members

Latest FME

Terms & ConditionsCookie settingsAccessibility statement
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.