Skip to main content
Open

Only use Dynamic Engine when no Standard Engine is available

Related products:FME Flow
  • August 28, 2020
  • 1 reply
  • 30 views

g_karssenberg
Contributor
Forum|alt.badge.img+9

Currently FME Server is routing jobs to available engines with the round robin circulation. One of the main benefits of dynamic engines is that job can use these (only) if there is peak demand. Currently jobs can also be assigned to dynamic engines if a standard engine is available but the circulation system decides to use the dynamic engine.

My suggestion is to have FME Server 'see' dynamic engines differently than standard engines to be able to only assign jobs to dynamic engines if no standard engine is available.

With this we don't have to pay for standard engines that are idle most of the time, can use dynamic engines only when needed and we don't lose credits on using dynamic engines when a standard engine is available.

See also discussion here.

1 reply

alexbiz
Influencer
Forum|alt.badge.img+33
  • Influencer
  • May 6, 2026

+1, one of our users has the exact same need with one static engine and ten dynamic engines.

This idea is also raised in this related post by ​@dbaldacchino1 :
https://community.safe.com/ideas/job-queues-order-of-engine-assignment-28587 

Where the request is specifically to define an order of preference for engine assignment within a queue. Unfortunately it was closed with just a link to the documentation, which does not address the actual ask.
 

The feature we need is simple: engines in a queue should be assignable in a defined priority order. FME Flow would assign jobs to the first available engine in that order: static engines first, dynamic ones as fallback. No credits spent when a static engine is free.

 

Hope this gets reconsidered!