Skip to main content
Archived

Workspaces to start running as soon as the Run button is pressed

Related products:FME Form
danilo_fme
svantepanter
  • danilo_fme
    danilo_fme
  • svantepanter
    svantepanter
michaelfitzpatr
Contributor

It would be great if workspaces ran as soon as you hit the run button. At the moment the larger the workspace the longer it takes for FME to start the translation.

This makes testing and authoring inconvenient as it takes a lot longer to run simple tasks.

Scenario: run a workspace with only a 'Creator' enabled

Large workspace: takes 12 seconds to start

Starting translation... 2017-09-06 11:00:45|  12.0| 12.0|INFORM|FME 2017.1.0.0 (20170731 - Build 17539 - WIN64)

Small workspace: runs instantly

Starting translation... 2017-09-06 11:01:25|   0.0|  0.0|INFORM|FME 2017.1.0.0 (20170731 - Build 17539 - WIN64)

This post is closed to further activity.
It may be a question with a best answer, an implemented idea, or just a post needing no comment.
If you have a follow-up or related question, 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.

10 replies

geosander
Forum|alt.badge.img+7
  • geosander
  • September 6, 2017

Wow, 12 seconds! Just how big is that workspace? I had a monster workspace too, but that "only" took 8 seconds to actually start running.

I also noticed an increased startup time between 2016 and 2017, which I already reported some time ago. That 8 seconds I mentioned used to take 4 with FME 2016. What was even stranger, was that the startup time was again twice as much on FME Server (so 8 seconds with FME 2016 and 16 (!) with FME 2017).

mark2atsafe
Safer
Forum|alt.badge.img+43
  • mark2atsafeSafer
  • Safer
  • September 6, 2017
Do you have Tools > FME Options > Workbench > "Autosave workspace before running translation" turned on? I can see that would take a while. Or any startup scripts? Even without, I suspect FME is saving a copy of the workspace and the bigger the file the longer it would take. Does it take 12 seconds when you choose File > Save?

 

michaelfitzpatr
Contributor
Forum|alt.badge.img
"Do you have Tools > FME Options > Workbench > "Autosave workspace before running translation" turned on?"

 

  • No

 

"Or any startup scripts?"

 

  • No

 

"Does it take 12 seconds when you choose File > Save?"

 

  • If I choose 'File > Save' the workspace saves instantly. If I then press run it still takes 12 seconds to start the translation
The workspace is 11MB in size.
lifalin2016
Contributor
Forum|alt.badge.img+29
  • lifalin2016Contributor
  • Contributor
  • September 7, 2017
As I understand the process, Workbench creates a temp FME mapping file on the fly when you press Run, based on the current workspace, and executes this. That's why you can edit certain parts of the workspace while it's running. If your workspace is very large, this export will take longer time.

 

 

-- Cheers, Lars I.
michaelfitzpatr
Contributor
Forum|alt.badge.img
Thanks for the info @lifalin2016 that would explain the current behaviour alright. I would still suggest an enhancement to improve the runtime performance so that X seconds becomes 0 seconds. There's scope to improve the performance. (ignoring the realities of effort to implement)

 

geosander
Forum|alt.badge.img+7
  • geosander
  • September 8, 2017
Yes, it's those "wb-xlate-...." files you sometimes see in your Finder/Explorer.

 

roland.martin
Forum|alt.badge.img+9
I've just checked through a load of my recent workspaces - I couldn't find one bigger than about 800KB. And just for context, I've been using FME for 12 years and do a lot of very hefty data transformation. I've literally no clue how you could get an FMW to be that big!

 

 

Have you tried sending it to Safe to see if they can fine tune it at all?
fmelizard
Contributor
Forum|alt.badge.img+17
  • fmelizardContributor
  • Contributor
  • September 16, 2017

We'd love to get our hands on your big workspace to see what we could do. When you hit run, we do rewrite the workspace. And then the FME engine has to parse it. So the first game to play is to figure out if it is the writing or the reading that is slow.

This does sound like an extreme case. Which is the VERY best kind. If you @michaelfitzpatr can, please do send it in to support@safe.com

C
Forum|alt.badge.img
  • c4
  • September 20, 2017

I researched our biggest workbench...over 22mb. The last time I ran this workbench was in 2013, on FME2012. Based on the log I have on file, startup time was a little over 3 seconds. Not sure if that has any relevancy now, but it's interesting.

My most recent, big workspace that I've run was 15mb on FME2014SP4. Startup time was 1.1 seconds.

michaelfitzpatr
Contributor
Forum|alt.badge.img
No problem, I've sent it on it's way to support :)

 

 

Helpful Members This Week

Community Stats

30,985
Posts
117,431
Replies
38,764
Members

Latest FME

Terms & ConditionsCookie settings

Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie 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.