Skip to main content
Solved

UpdateDetector much slower in FME 2017

  • November 21, 2017
  • 2 replies
  • 25 views
erik_jan
Contributor
Forum|alt.badge.img+22

For a customer I had to exchange the FME 2015 UpdateDetector in a workspace with the FME 2017 version of the same transformer.

I have copied the same settings from the FME 2015 transformer and use the same dataset.

The performance for the workspace went from 5 minutes to 50 minutes, and a lot more (75%) updates were detected.

Has anybody the same experience with this custom transformer.

Just wondering what could cause changes to be detected with the new transformer that were not detected with the older version.

Any suggestions are appreciated.

Best answer by erik_jan

The issue seems to be with the comparison of an attribute that has a different data_type in the sources:

Source 1 (Oracle) is Number(20,8), Source 2 (SDE) is double.

Even though the values are exactly the same, the records are detected as updates.

At the end it is the updates that are slowing down the workflow.

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.

2 replies

erik_jan
Contributor
Forum|alt.badge.img+22
  • erik_janContributor
  • Author
  • Contributor
  • 2179 replies
  • Best Answer
  • November 21, 2017

The issue seems to be with the comparison of an attribute that has a different data_type in the sources:

Source 1 (Oracle) is Number(20,8), Source 2 (SDE) is double.

Even though the values are exactly the same, the records are detected as updates.

At the end it is the updates that are slowing down the workflow.

erik_jan
Contributor
Forum|alt.badge.img+22
  • erik_janContributor
  • Author
  • Contributor
  • 2179 replies
  • November 22, 2017

The issue seems to be with the comparison of an attribute that has a different data_type in the sources:

Source 1 (Oracle) is Number(20,8), Source 2 (SDE) is double.

Even though the values are exactly the same, the records are detected as updates.

At the end it is the updates that are slowing down the workflow.

Fixing the data_type issue solved the workspace performance issue.

 

Issued a call to Safe Support about this.

 

 

Community Stats

32,090
Posts
121,869
Replies
39,731
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.