I am running a Workspace and after a while it gives an error and as if the memory had burst, is there any way to control memory?
Best Answer
Control FME Desktop memory usage
Best answer by david_r
My top six tips, in no particular order off the top of my head:
- Unblock your transformers as much as possible
- If you have multiple writers, replace them with FeatureWriters
- Only read what you need, where-clauses are your friend
- Let the database do the heavy lifting, e.g. a join on two database tables is a whole lot quicker than a FeatureMerger
- Only keep the attributes you need at each step of the way (AttributeKeeper, yay)
- Try to avoid the ListExploder on huge numbers of features/items, if possible
Also, consider 64-bit FME.
This post is closed to further activity.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, 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.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, 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.
- Best Answer
My top six tips, in no particular order off the top of my head:
- Unblock your transformers as much as possible
- If you have multiple writers, replace them with FeatureWriters
- Only read what you need, where-clauses are your friend
- Let the database do the heavy lifting, e.g. a join on two database tables is a whole lot quicker than a FeatureMerger
- Only keep the attributes you need at each step of the way (AttributeKeeper, yay)
- Try to avoid the ListExploder on huge numbers of features/items, if possible
Also, consider 64-bit FME.
My top six tips, in no particular order off the top of my head:
- Unblock your transformers as much as possible
- If you have multiple writers, replace them with FeatureWriters
- Only read what you need, where-clauses are your friend
- Let the database do the heavy lifting, e.g. a join on two database tables is a whole lot quicker than a FeatureMerger
- Only keep the attributes you need at each step of the way (AttributeKeeper, yay)
- Try to avoid the ListExploder on huge numbers of features/items, if possible
Also, consider 64-bit FME.
- try avoiding Data Inspectors or keep it at places, only where you need it
- check space on your hard disk
- In Tools-->FME Options-->Translation set Translation Priority to HIGH, in case, your are running some concurent tasks.