+1I use WorkspaceRunner in master workspace to run some specific tiling operation by slave workspace.
Nothing special. Slave workspaces are done about several seconds each. Workbench run only one fme.exe process no matter what is set in WorkspaceRunner transformer. Any idea what can be the reason?
Have you set "Wait for job to complete" to Yes? If so, the master will only be able to run one child workspace at at time.
If you set it to No you will be able to run a maximum of 7 concurrent child workspaces. This is a licensing limitation.
I'm assuming you don't have FME Server in the mix.
+1Have you set "Wait for job to complete" to Yes? If so, the master will only be able to run one child workspace at at time.
If you set it to No you will be able to run a maximum of 7 concurrent child workspaces. This is a licensing limitation.
I'm assuming you don't have FME Server in the mix.
"Waiting for job to complete" option is not the reason. No FME Server to use
"Waiting for job to complete" option is not the reason. No FME Server to use
Wait for job to complete is also used for FME Desktop.
+1Have you set "Wait for job to complete" to Yes? If so, the master will only be able to run one child workspace at at time.
If you set it to No you will be able to run a maximum of 7 concurrent child workspaces. This is a licensing limitation.
I'm assuming you don't have FME Server in the mix.
I know that option and parrarel processes limitations according to license type. I've no idea what is wrong with just those workspaces. I have no such problem with other.
I know that option and parrarel processes limitations according to license type. I've no idea what is wrong with just those workspaces. I have no such problem with other.
It's a bit difficult to say without knowing the workspace, but it is possible that your trigger features aren't coming fast enough to the WorkspaceRunner for some reason?
What happens if you insert a FeatureHolder just before the WorkspaceRunner? Does that change anything?
+1Have you set "Wait for job to complete" to Yes? If so, the master will only be able to run one child workspace at at time.
If you set it to No you will be able to run a maximum of 7 concurrent child workspaces. This is a licensing limitation.
I'm assuming you don't have FME Server in the mix.
Please take a look to attached workspaces. Master workspace run slave ones. General functionality is creation raster tiles from vector tiles
+15hi, i tried your workspace using fme 2016 and it does open concurrent workspaces.
I see no problem.
+1@gio have right. When I placed Decelerator then FME has opened all concurrent workspaces. BTW if slave script is quite quick FME do not use all processor cores to process workspaces in parallel mode.
@gio have right. When I placed Decelerator then FME has opened all concurrent workspaces. BTW if slave script is quite quick FME do not use all processor cores to process workspaces in parallel mode.
That could also just be the operating system, as I'm not sure FME has any say in which process is running on which core.
