You have to add it to the workspace header, see under Tools / Edit header... in FME Workbench, e.g.
When you execute the workspace you will see that it's mentioned somewhere at the start of the log:
You have to add it to the workspace header, see under Tools / Edit header... in FME Workbench, e.g.
When you execute the workspace you will see that it's mentioned somewhere at the start of the log:
@david_r has hit the nail on the head!
@lifalin2016 - The FME_ENGINE_MEMORY_REDLINE configuration, for FME Desktop, is discussed in
this Knowledge Center article (see bottom).
@lifalin2016, What version of FME is involved here?
I'm curious if it is FME 2017 and if you might be interested in testing FME 2018 beta?
I want to add that this parameter is not a 'fix', rather it helps FME influence its use of memory resources. We might say that we would discourage users from changing the default value and instead determine if there are other ways to avoid the memory issue.
From time to time changes are made in the product that may not have the desired affect on the performance and some workflows could be impacted. If this is one of those examples please don't hesitate to share with support at support@safe.com to help investigate.
For the record changes were made in FME 2017 that reduced this settings effectiveness on influencing FME's use of memory resources. Further, in FME 2017 changes were made that pushed the memory resource management to the OS.
In FME 2018 we have returned the memory resource management to FME do to some technical issues that limited us on further improving issues around memory related topics.
You have to add it to the workspace header, see under Tools / Edit header... in FME Workbench, e.g.
When you execute the workspace you will see that it's mentioned somewhere at the start of the log:
Moving forward we would discourage the use of this parameter as a first step in resolving a memory issue with an FME Workspace. I is absolutely a last resort and should not be adjusted until it is recommended by Safe Support.
We recommend working in the confines of the workspace by making changes to the workflow, Readers/Writers, or Transformers or increasing the memory of the system in question (FME 64 bit). If this doesn't resolve the memory problem then please report the issue to Safe Support (support@safe.com) and we will work on improving FME.
@david_r has hit the nail on the head!
@lifalin2016 - The FME_ENGINE_MEMORY_REDLINE configuration, for FME Desktop, is discussed in
this Knowledge Center article (see bottom).
Hi Rylan.
I did see that article, but it uses the term "FME Engine", which is normally associated with FME Server, not Desktop. And it has no mention of how to apply this in the desktop application as such.
You have to add it to the workspace header, see under Tools / Edit header... in FME Workbench, e.g.
When you execute the workspace you will see that it's mentioned somewhere at the start of the log:
Thanks David.
Ok, manually edit what appears to be an auto-generated header portion ??
This doesn't sound like a sound implementation, but if it works, great.
However, Steve says below, that this feature will be discouraged (and discontinued?) in future versions ? Will it be replaced by something better I wonder (and sincerely hope so) ?
Because, as I see it, just adding more RAM may not be an option. E.g., my desktop machine maxes out with 16 Gb (tell me about it), so that path would be exhausted on it. So some sort of mechanism to limit how many resources each FME session may consume (apart from hard drive space) is still necessary in a production setup. An FME Server would of course be better and very nice, but we don't have the volume for that investment just yet.
Cheers
Thanks David.
Ok, manually edit what appears to be an auto-generated header portion ??
This doesn't sound like a sound implementation, but if it works, great.
However, Steve says below, that this feature will be discouraged (and discontinued?) in future versions ? Will it be replaced by something better I wonder (and sincerely hope so) ?
Because, as I see it, just adding more RAM may not be an option. E.g., my desktop machine maxes out with 16 Gb (tell me about it), so that path would be exhausted on it. So some sort of mechanism to limit how many resources each FME session may consume (apart from hard drive space) is still necessary in a production setup. An FME Server would of course be better and very nice, but we don't have the volume for that investment just yet.
Cheers
I suspect modifying the header isn't meant to be something you do, unless you're trying to debug something out of the ordinary.
I agree with Steve that you should probably look into how your workspace has been authored before playing around with this setting. Tip: Blocking transformers are horrible for memory consumpting when dealing with large datasets. See here for a starting point on how to un-block them:
https://knowledge.safe.com/articles/38700/clearing-blocking-transformers.html
Hi Rylan.
I did see that article, but it uses the term "FME Engine", which is normally associated with FME Server, not Desktop. And it has no mention of how to apply this in the desktop application as such.
Hi @lifalin2016 - I am sorry about the terminology confusion. Both FME Desktop and FME Server are powered by the 'FME Engine'.
The header I am referring to for the article I referenced above is "Controlling How FME Engine Consumes Memory" – it's in the very last paragraph: "To set this value in FME Workbench use Tools - Edit Header and enter: FME_ENGINE_MEMORY_REDLINE 0.5 as the very first line." Hope that helps! I'm sorry about the ambiguity. I referenced the article instead of simply pasting in here because the article contains important information concerning the parameter.
As @SteveAtSafe has mentioned this parameter is really the "last resort". It would be great if you opened a
support ticket so that we can have our developers investigate if there are any improvements we can make to the product.
