Skip to main content
Solved

FME Server CPU (Dynamic Engines) ≈ FME Cloud?

  • December 15, 2022
  • 3 replies
  • 81 views

dejan11
Contributor
Forum|alt.badge.img+12

As far as I understood from the documentation, the self-hosted FME Server (installed on my own server) can be also licensed by CPU (Dynamic Engines)?

That means that I have a full control and security (especially in terms of data privacy, etc) of FME Server like self-hosted FME Server with standard engine(s), however in terms of license it acts similar to FME Cloud?

So if both questions are correct then the difference between self-hosted FME Server licensed by standard engine(s) and self-hosted FME Server licensed by CPU (dynamic engines) in regards to license is that the client pays for an extra standard engine only once, but for CPU Usage as long it in hours takes - continuous payment?

Best answer by redgeographics

dejan11 wrote:

OK, thanks. But in regards to system requirements there is no difference between self-hosted FME Server standard engine(s) and self-hosted FME Server with dynamic engines, right?

For both installations we have to estimate the traffic i.e number of tasks being executed at the same time and take care of CPUs etc (https://community.safe.com/s/article/FME-Server-Host-System-Sizing) equally?

Yes, they're identical in that regard.

View original
Did this help you find an answer to your question?

3 replies

redgeographics
Celebrity
Forum|alt.badge.img+48

An FME Server with CPU licensing (Dynamic engines) is not exactly the same as FME Cloud. The CPU licensing credits are only used when there's actual jobs running, whereas the FME Cloud is being charged either per year or, if you do it on demand, per hour that the the machine is on, regardless of whether or not it's actually running jobs.

 

A standard engine is indeed only paid once (and then there's the annual maintenance), CPU usage is processing time that you're buying. Licensing-wise there is no limit to the number of engines you can have running with CPU licensing, which means it's best used to deal with peaks of high demand. Standard engines are better when the demand is relatively stable over time.


dejan11
Contributor
Forum|alt.badge.img+12
  • Author
  • Contributor
  • December 16, 2022
redgeographics wrote:

An FME Server with CPU licensing (Dynamic engines) is not exactly the same as FME Cloud. The CPU licensing credits are only used when there's actual jobs running, whereas the FME Cloud is being charged either per year or, if you do it on demand, per hour that the the machine is on, regardless of whether or not it's actually running jobs.

 

A standard engine is indeed only paid once (and then there's the annual maintenance), CPU usage is processing time that you're buying. Licensing-wise there is no limit to the number of engines you can have running with CPU licensing, which means it's best used to deal with peaks of high demand. Standard engines are better when the demand is relatively stable over time.

OK, thanks. But in regards to system requirements there is no difference between self-hosted FME Server standard engine(s) and self-hosted FME Server with dynamic engines, right?

For both installations we have to estimate the traffic i.e number of tasks being executed at the same time and take care of CPUs etc (https://community.safe.com/s/article/FME-Server-Host-System-Sizing) equally?


redgeographics
Celebrity
Forum|alt.badge.img+48
  • Celebrity
  • Best Answer
  • December 16, 2022
dejan11 wrote:

OK, thanks. But in regards to system requirements there is no difference between self-hosted FME Server standard engine(s) and self-hosted FME Server with dynamic engines, right?

For both installations we have to estimate the traffic i.e number of tasks being executed at the same time and take care of CPUs etc (https://community.safe.com/s/article/FME-Server-Host-System-Sizing) equally?

Yes, they're identical in that regard.


Reply


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