Skip to main content
Solved

whats does "Features are being recorded on all output ports" mean?

  • February 17, 2022
  • 1 reply
  • 488 views
B

Hello, i have a point cloud data file in e57 format and i plan to reduce it by transform PointCloudSimplifier. There is my workspace.1And it appears that warning "The workspace may run slower because features are being recorded on all output ports". The data is very large, more than 100GB, so i wish it cloud be processed faster.

​

I'm not exactly sure what "recorded on all output ports" means, what should i do? Do i need to add a transform like AttributeManager between the Reader and PointCloudSimplifier or something else?

Thank you in advance!

Best answer by nielsgerrits

The complete log is:

Feature Caching is ON
The workspace may run slower because features are being recorded on all output ports.

Feature Caching means that at each transformer, all data at all outputports is written to temp files. This way, after a workspace is run, you can inspect all data at every transformer. Since Safe introduced Feature Caching in 2018 this setting is switched on by default. See the blog post Feature Caching: A New Mode for FME Workspace Authoring for more details.

 

While this is very useful when developing a workspace with light sample datasets, it can come at a great cost in performance due to massive amounts of I/O.

 

You can simply disable Feature Caching via Run --> Enable Feature Caching.

 

It is also possible to disable Feature Caching for some parts of your workspace using bookmarks. The outputports of transformers in a closed bookmark will not be cached. Personally, I don't like how layout of the transformers are restored when re opening the bookmark, so I never use this functionality.

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.

1 reply

nielsgerrits
VIP
Forum|alt.badge.img+60
  • nielsgerritsVIP
  • 2938 replies
  • Best Answer
  • February 17, 2022

The complete log is:

Feature Caching is ON
The workspace may run slower because features are being recorded on all output ports.

Feature Caching means that at each transformer, all data at all outputports is written to temp files. This way, after a workspace is run, you can inspect all data at every transformer. Since Safe introduced Feature Caching in 2018 this setting is switched on by default. See the blog post Feature Caching: A New Mode for FME Workspace Authoring for more details.

 

While this is very useful when developing a workspace with light sample datasets, it can come at a great cost in performance due to massive amounts of I/O.

 

You can simply disable Feature Caching via Run --> Enable Feature Caching.

 

It is also possible to disable Feature Caching for some parts of your workspace using bookmarks. The outputports of transformers in a closed bookmark will not be cached. Personally, I don't like how layout of the transformers are restored when re opening the bookmark, so I never use this functionality.

Buckle your seatbelt Dorothy, cause Kansas is going bye-bye...

Community Stats

32,070
Posts
121,770
Replies
39,694
Members

Latest FME

Terms & ConditionsCookie settingsAccessibility statement
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.