Skip to main content
  • EN

Hi.

First let me say, that I absolutely love the incremental run abilities added to 2020. It makes incremental building and debugging workspace a breaze.

However, production runs are a different matter. Here one always runs the full workspace and as fast as possible. I.e. no caching.

I often utilize a master-slave workspace setup, where one workspace calls other workspaces as needed.

Now, the caching is a Workbench setting, and cannot be set for a workspace, but does it only apply to the master workspace being run directly, or does it also apply to the initiated workspace that are called by the master workspace ?

Cheers.

Na it will only apply to the process called by the worksapce opened in FME Workbench. Plus you can turn it off

Na it will only apply to the process called by the worksapce opened in FME Workbench. Plus you can turn it off

Feature caching in the master workspace is often of lesser concern, than feature caching in the typically heavier slave workspaces. I hope you're right.

Feature caching in the master workspace is often of lesser concern, than feature caching in the typically heavier slave workspaces. I hope you're right.

FME 2019 and FME 2018 also had feature caching and partial runs and it didn't effect production. Jobs on FME Server also are not effected by feature caching.

 

 

I'm 99.9999% sure that you only get caching when the workspace is open in Workbench. But you could easily check the log file for the second workspace, and see what it says. You'd get lines like this:

Stored x feature(s) to FME feature store file `C:\Users\mark\AppData\Local\Temp\wb-cache--RMnOhj
...if caching were happening.

Reply


Community Stats

30,159
Posts
114,479
Replies
37,803
Members
Terms & ConditionsCookie settings
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.